• ホーム
  • ブログ
  • [2023年12月]更新のGoogle Professional-Cloud-DevOps-Engineer試験基本問題には解答が付きます [Q61-Q77]

[2023年12月]更新のGoogle Professional-Cloud-DevOps-Engineer試験基本問題には解答が付きます [Q61-Q77]

Share

[2023年12月]更新のGoogle Professional-Cloud-DevOps-Engineer試験基本問題には解答が付きます

2023年最新の実際に出るGoogle Professional-Cloud-DevOps-Engineer試験問題集と解答


Google Professional-Cloud-Devops-Engineer（Google Cloud Certified-Professional Cloud Devops Engineer）認定試験は、Cloud Devops Engineeringの分野の専門家にとって非常に人気のある認定です。この認定はGoogle Cloudによって提供されており、Google Cloudプラットフォームでアプリケーションの展開、監視、管理における個人のスキルと専門知識を検証するように設計されています。

 

質問 # 61
You want to share a Cloud Monitoring custom dashboard with a partner team What should you do?

  • A. Provide the partner team with the dashboard URL to enable the partner team to create a copy of the dashboard
  • B. Export the metrics to BigQuery Use Looker Studio to create a dashboard, and share the dashboard with the partner team
  • C. Copy the Monitoring Query Language (MQL) query from the dashboard; and send the MQL query to the partner team
  • D. Download the JSON definition of the dashboard, and send the JSON file to the partner team

正解：A

解説：
Explanation
The best option for sharing a Cloud Monitoring custom dashboard with a partner team is to provide the partner team with the dashboard URL to enable the partner team to create a copy of the dashboard. A Cloud Monitoring custom dashboard is a dashboard that allows you to create and customize charts and widgets to display metrics, logs, and traces from your Google Cloud resources and applications. You can share a custom dashboard with a partner team by providing them with the dashboard URL, which is a link that allows them to view the dashboard in their browser. The partner team can then create a copy of the dashboard in their own project by using the Copy Dashboard option. This way, they can access and modify the dashboard without affecting the original one.


質問 # 62
You use a multiple step Cloud Build pipeline to build and deploy your application to Google Kubernetes Engine (GKE). You want to integrate with a third-party monitoring platform by performing a HTTP POST of the build information to a webhook. You want to minimize the development effort. What should you do?

  • A. Create a Cloud Pub/Sub push subscription to the Cloud Build cloud-builds PubSub topic to HTTP POST the build information to a webhook.
  • B. Add logic to each Cloud Build step to HTTP POST the build information to a webhook.
  • C. Use Stackdriver Logging to create a logs-based metric from the Cloud Buitd logs. Create an Alert with a Webhook notification type.
  • D. Add a new step at the end of the pipeline in Cloud Build to HTTP POST the build information to a webhook.

正解：A


質問 # 63
You are deploying an application that needs to access sensitive information. You need to ensure that this information is encrypted and the risk of exposure is minimal if a breach occurs. What should you do?

  • A. Store the encryption keys in Cloud Key Management Service (KMS) and rotate the keys frequently
  • B. Integrate the application with a Single sign-on (SSO) system and do not expose secrets to the application
  • C. Inject the secret at the time of instance creation via an encrypted configuration management system.
  • D. Leverage a continuous build pipeline that produces multiple versions of the secret for each instance of the application.

正解：A


質問 # 64
You use Cloud Build to build and deploy your application. You want to securely incorporate database credentials and other application secrets into the build pipeline. You also want to minimize the development effort. What should you do?

  • A. Use client-side encryption to encrypt the secrets and store them in a Cloud Storage bucket. Store a decryption key in the bucket and grant Cloud Build access to the bucket.
  • B. Encrypt the secrets and store them in the application repository. Store a decryption key in a separate repository and grant Cloud Build access to the repository.
  • C. Create a Cloud Storage bucket and use the built-in encryption at rest. Store the secrets in the bucket and grant Cloud Build access to the bucket.
  • D. Use Cloud Key Management Service (Cloud KMS) to encrypt the secrets and include them in your Cloud Build deployment configuration. Grant Cloud Build access to the KeyRing.

正解：D

解説：
https://cloud.google.com/build/docs/securing-builds/use-encrypted-credentials


質問 # 65
You are building an application that runs on Cloud Run The application needs to access a third-party API by using an API key You need to determine a secure way to store and use the API key in your application by following Google-recommended practices What should you do?

  • A. Save the API key in Secret Manager as a secret Reference the secret as an environment variable in the Cloud Run application
  • B. Encrypt the API key by using Cloud Key Management Service (Cloud KMS) and pass the key to Cloud Run as an environment variable Decrypt and use the key in Cloud Run
  • C. Save the API key in Cloud Key Management Service (Cloud KMS) as a key Reference the key as an environment variable in the Cloud Run application
  • D. Save the API key in Secret Manager as a secret key Mount the secret key under the /sys/api_key directory and decrypt the key in the Cloud Run application

正解：A

解説：
Explanation
The best option for storing and using the API key in your application by following Google-recommended practices is to save the API key in Secret Manager as a secret and reference the secret as an environment variable in the Cloud Run application. Secret Manager is a service that allows you to store and manage sensitive data, such as API keys, passwords, and certificates, in Google Cloud. A secret is a resource that represents a logical secret, such as an API key. You can save the API key in Secret Manager as a secret and use IAM policies to control who can access it. You can also reference the secret as an environment variable in the Cloud Run application by using the ${SECRET_NAME} syntax. This way, you can securely store and use the API key in your application without exposing it in your code or configuration files.


質問 # 66
You recently migrated an ecommerce application to Google Cloud. You now need to prepare the application for the upcoming peak traffic season. You want to follow Google-recommended practices. What should you do first to prepare for the busy season?

  • A. Load test the application to profile its performance for scaling.
  • B. Create a Terraform configuration for the application's underlying infrastructure to quickly deploy to additional regions.
  • C. Pre-provision the additional compute power that was used last season, and expect growth.
  • D. Migrate the application to Cloud Run, and use autoscaling.

正解：A

解説：
Explanation
The first thing you should do to prepare your ecommerce application for the upcoming peak traffic season is to load test the application to profile its performance for scaling. Load testing is a process of simulating high traffic or user demand on your application and measuring how it responds. Load testing can help you identify any bottlenecks, errors, or performance issues that might affect your application during the busy season1. Load testing can also help you determine the optimal scaling strategy for your application, such as horizontal scaling (adding more instances) or vertical scaling (adding more resources to each instance)2.
There are different tools and methods for load testing your ecommerce application on Google Cloud, depending on the type and complexity of your application. For example, you can use Cloud Load Balancing to distribute traffic across multiple instances of your application, and use Cloud Monitoring to measure the latency, throughput, and error rate of your application3. You can also use Cloud Functions or Cloud Run to create serverless load generators that can simulate user requests and send them to your application4.
Alternatively, you can use third-party tools such as Apache JMeter or Locust to create and run load tests on your application.
By load testing your ecommerce application before the peak traffic season, you can ensure that your application is ready to handle the expected load and provide a good user experience. You can also use the results of your load tests to plan and implement other steps to prepare your application for the busy season, such as migrating to a more scalable platform, creating a Terraform configuration for deploying to additional regions, or pre-provisioning additional compute power.
References:
1: Load Testing 101: How To Test Website Performance | BlazeMeter
2: Scaling applications | Google Cloud
3: Load testing using Google Cloud | Solutions | Google Cloud
4: Serverless load testing using Cloud Functions | Solutions | Google Cloud


質問 # 67
You use Cloud Build to build and deploy your application. You want to securely incorporate database credentials and other application secrets into the build pipeline. You also want to minimize the development effort. What should you do?

  • A. Use client-side encryption to encrypt the secrets and store them in a Cloud Storage bucket. Store a decryption key in the bucket and grant Cloud Build access to the bucket.
  • B. Encrypt the secrets and store them in the application repository. Store a decryption key in a separate repository and grant Cloud Build access to the repository.
  • C. Create a Cloud Storage bucket and use the built-in encryption at rest. Store the secrets in the bucket and grant Cloud Build access to the bucket.
  • D. Use Cloud Key Management Service (Cloud KMS) to encrypt the secrets and include them in your Cloud Build deployment configuration. Grant Cloud Build access to the KeyRing.

正解：D


質問 # 68
You manage an application that runs in Google Kubernetes Engine (GKE) and uses the blue/green deployment methodology Extracts of the Kubernetes manifests are shown below

The Deployment app-green was updated to use the new version of the application During post-deployment monitoring you notice that the majority of user requests are failing You did not observe this behavior in the testing environment You need to mitigate the incident impact on users and enable the developers to troubleshoot the issue What should you do?

  • A. Change the selector on the Service app-2vc to app: my-app.
  • B. Change the selector on the Service app-svc to app: my-app, version: blue
  • C. Update the Deployment app-blue to use the new version of the application
  • D. Update the Deployment ape-green to use the previous version of the application

正解：B

解説：
Explanation
The best option for mitigating the incident impact on users and enabling the developers to troubleshoot the issue is to change the selector on the Service app-svc to app: my-app, version: blue. A Service is a resource that defines how to access a set of Pods. A selector is a field that specifies which Pods are selected by the Service. By changing the selector on the Service app-svc to app: my-app, version: blue, you can ensure that the Service only routes traffic to the Pods that have both labels app: my-app and version: blue. These Pods belong to the Deployment app-blue, which uses the previous version of the application. This way, you can mitigate the incident impact on users by switching back to the working version of the application. You can also enable the developers to troubleshoot the issue with the new version of the application in the Deployment app-green without affecting users.


質問 # 69
You use a multiple step Cloud Build pipeline to build and deploy your application to Google Kubernetes Engine (GKE). You want to integrate with a third-party monitoring platform by performing a HTTP POST of the build information to a webhook. You want to minimize the development effort. What should you do?

  • A. Add logic to each Cloud Build step to HTTP POST the build information to a webhook.
  • B. Use Stackdriver Logging to create a logs-based metric from the Cloud Buitd logs. Create an Alert with a Webhook notification type.
  • C. Create a Cloud Pub/Sub push subscription to the Cloud Build cloud-builds PubSub topic to HTTP POST the build information to a webhook.
  • D. Add a new step at the end of the pipeline in Cloud Build to HTTP POST the build information to a webhook.

正解：D


質問 # 70
Your company follows Site Reliability Engineering practices. You are the person in charge of Communications for a large, ongoing incident affecting your customer-facing applications. There is still no estimated time for a resolution of the outage. You are receiving emails from internal stakeholders who want updates on the outage, as well as emails from customers who want to know what is happening. You want to efficiently provide updates to everyone affected by the outage. What should you do?

  • A. Provide periodic updates to all stakeholders in a timely manner. Commit to a "next update" time in all communications.
  • B. Focus on responding to internal stakeholders at least every 30 minutes. Commit to "next update" times.
  • C. Delegate the responding to internal stakeholder emails to another member of the Incident Response Team. Focus on providing responses directly to customers.
  • D. Provide all internal stakeholder emails to the Incident Commander, and allow them to manage internal communications. Focus on providing responses directly to customers.

正解：B


質問 # 71
Your uses Jenkins running on Google Cloud VM instances for CI/CD. You need to extend the functionality to use infrastructure as code automation by using Terraform. You must ensure that the Terraform Jenkins instance is authorized to create Google Cloud resources. You want to follow Google-recommended practices- What should you do?

  • A. Add the auth application-default command as a step in Jenkins before running the Terraform commands.
  • B. Create a dedicated service account for the Terraform instance. Download and copy the secret key value to the GOOGLE environment variable on the Jenkins server.
  • C. Confirm that the Jenkins VM instance has an attached service account with the appropriate Identity and Access Management (IAM) permissions.use the Terraform module so that Secret Manager can retrieve credentials.

正解：C

解説：
The correct answer is C.
Confirming that the Jenkins VM instance has an attached service account with the appropriate Identity and Access Management (IAM) permissions is the best way to ensure that the Terraform Jenkins instance is authorized to create Google Cloud resources. This follows the Google-recommended practice of using service accounts to authenticate and authorize applications running on Google Cloud1. Service accounts are associated with private keys that can be used to generate access tokens for Google Cloud APIs2. By attaching a service account to the Jenkins VM instance, Terraform can use the Application Default Credentials (ADC) strategy to automatically find and use the service account credentials3.
Answer A is incorrect because the auth application-default command is used to obtain user credentials, not service account credentials. User credentials are not recommended for applications running on Google Cloud, as they are less secure and less scalable than service account credentials1.
Answer B is incorrect because it involves downloading and copying the secret key value of the service account, which is not a secure or reliable way of managing credentials. The secret key value should be kept private and not exposed to any other system or user2. Moreover, setting the GOOGLE environment variable on the Jenkins server is not a valid way of providing credentials to Terraform. Terraform expects the credentials to be either in a file pointed by the GOOGLE_APPLICATION_CREDENTIALS environment variable, or in a provider block with the credentials argument3.
Answer D is incorrect because it involves using the Terraform module for Secret Manager, which is a service that stores and manages sensitive data such as API keys, passwords, and certificates. While Secret Manager can be used to store and retrieve credentials, it is not necessary or sufficient for authorizing the Terraform Jenkins instance. The Terraform Jenkins instance still needs a service account with the appropriate IAM permissions to access Secret Manager and other Google Cloud resources.


質問 # 72
You have a CI/CD pipeline that uses Cloud Build to build new Docker images and push them to Docker Hub. You use Git for code versioning. After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline. You need to resolve the issue following Site Reliability Engineering practices. What should you do?

  • A. Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.
  • B. Disable the CI pipeline and revert to manually building and pushing the artifacts.
  • C. Change the CI pipeline to push the artifacts to Container Registry instead of Docker Hub.
  • D. Upload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix the issue.

正解：A

解説：
"After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline"- means something wrong on the recent change not with the image registry.


質問 # 73
You encountered a major service outage that affected all users of the service for multiple hours. After several hours of incident management, the service returned to normal, and user access was restored. You need to provide an incident summary to relevant stakeholders following the Site Reliability Engineering recommended practices. What should you do first?

  • A. Require the engineer responsible to write an apology email to all stakeholders.
  • B. Call individual stakeholders lo explain what happened.
  • C. Develop a post-mortem to be distributed to stakeholders.
  • D. Send the Incident State Document to all the stakeholders.

正解：C


質問 # 74
You support a stateless web-based API that is deployed on a single Compute Engine instance in the europe-west2-a zone . The Service Level Indicator (SLI) for service availability is below the specified Service Level Objective (SLO). A postmortem has revealed that requests to the API regularly time out. The time outs are due to the API having a high number of requests and running out memory. You want to improve service availability. What should you do?

  • A. Set up additional service instances in other zones and use them as a failover in case the primary instance is unavailable.
  • B. Set up additional service instances in other zones and load balance the traffic between all instances.
  • C. Move the service to higher-specification compute instances with more memory.
  • D. Change the specified SLO to match the measured SLI.

正解：B


質問 # 75
You support an application deployed on Compute Engine. The application connects to a Cloud SQL instance to store and retrieve data. After an update to the application, users report errors showing database timeout messages. The number of concurrent active users remained stable. You need to find the most probable cause of the database timeout. What should you do?

  • A. Determine whether there is an increased number of connections to the Cloud SQL instance.
  • B. Check the serial port logs of the Compute Engine instance.
  • C. Use Stackdriver Profiler to visualize the resources utilization throughout the application.
  • D. Use Cloud Security Scanner to see whether your Cloud SQL is under a Distributed Denial of Service (DDoS) attack.

正解：A

解説：
Explanation
The most probable cause of the database timeout is an increased number of connections to the Cloud SQL instance. This could happen if the application does not close connections properly or if it creates too many connections at once. You can check the number of connections to the Cloud SQL instance using Cloud Monitoring or Cloud SQL Admin API .


質問 # 76
You are ready to deploy a new feature of a web-based application to production. You want to use Google Kubernetes Engine (GKE) to perform a phased rollout to half of the web server pods.
What should you do?

  • A. Use a partitioned rolling update.
  • B. Use a replica set in the deployment specification.
  • C. Use Node taints with NoExecute.
  • D. Use a stateful set with parallel pod management policy.

正解：A

解説：
https://medium.com/velotio-perspectives/exploring-upgrade-strategies-for-stateful-sets-in-kubernetes-c02b8286f251


質問 # 77
......

合格保証付きのCloud DevOps Engineer Professional-Cloud-DevOps-Engineer試験問題集：https://www.passtest.jp/Google/Professional-Cloud-DevOps-Engineer-shiken.html

Professional-Cloud-DevOps-Engineer練習テストエンジンで今すぐ使おう164試験問題：https://drive.google.com/open?id=1ZvrdFzmHQkIz5K06fPUgqsrt8TJhhpmW

関するブログ

もっと
Professional-Cloud-DevOps-Engineer 無料問題集