Professional-Cloud-DevOps-Engineer 無料問題集「Google Cloud Certified - Professional Cloud DevOps Engineer」

（A）Look through other metrics related to the product and find SLOs with remaining error budget.Reallocate the error budgets and allow the feature launch.

（B）Escalate the situation and request additional error budget.

（C）Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.

（D）Notify the team about the lack of error budget and ensure that all their tests are successful so the launch will not further risk the error budget.

（A）Use the Git history to find the related code commit. Prevent the engineer who made that commit from working on production services.

（B）Focus on identifying the contributing causes of the incident rather than the individual responsible for the cause.

（C）Plan individual meetings with all the engineers involved. Determine who approved and pushed the new release to production.

（D）Focus on developing new features rather than avoiding the outages from recurring.

（A）Create a Dataflow pipeline to analyze service metrics in real time.

（B）Use a distributed tracing framework such as OpenTelemetry or Stackdriver Trace.

（C）Analyze VPC flow logs along the path of the request.

（D）Investigate the Liveness and Readiness probes for each service.

（A）Upgrade your on-premises VMs to have faster CPUs and more memory.

（B）Configure Jenkins to use an artifact repository in your on-premises environment.

（C）Implement a blue-green deployment strategy for your on-premises VMs.

（D）Increase the number of Jenkins executor threads.

（A）Import the Stackdriver Debugger package, and configure the application to emit debug messages with timing information.

（B）Install an Application Performance Monitoring (APM) tool in both locations, and configure an export to a central data storage location for analysis.

（C）Instrument the code using a timing library, and publish the metrics via a health check endpoint that is scraped by Stackdriver.

（D）Import the Stackdriver Profiler package, and configure it to relay function timing data to Stackdriver for further analysis.

（A）Confirm that the Jenkins VM instance has an attached service account with the appropriate Identity and Access Management (IAM) permissions.

（B）use the Terraform module so that Secret Manager can retrieve credentials.

（C）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.

（D）Add the auth application-default command as a step in Jenkins before running the Terraform commands.

（A）Store the password directly in the code. Use Cloud Build to rebuild and deploy the application each time the password changes.

（B）Store the password in Secret Manager and send the secret to the application by using environment variables.

（C）Store the password in Secret Manager and mount the secret as a volume within the application.

（D）Use Cloud Build to add your password into the application container at build time. Ensure that Artifact Registry is secured from public access.

（A）Escalate the situation and request additional error budget.

（B）Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.

（C）Notify the team about the lack of error budget and ensure that all their tests are successful so the launch will not further risk the error budget.

（D）Look through other metrics related to the product and find SLOs with remaining error budget.
Reallocate the error budgets and allow the feature launch.

（A）Assign the Container Developer role to the Cloud Build service account.

（B）Create a new service account with the Container Developer role and use it to run Cloud Build.

（C）Specify the Container Developer role for Cloud Build in the cloudbuild.yaml file.

（D）Create a separate step in Cloud Build to retrieve service account credentials and pass these to kubectl.

（A）1 . Drain traffic from the unhealthy node and remove the old node from service.2. Add a new node to the pool, wait for the new node to report as healthy, and then serve traffic to the new node.3. Monitor traffic to ensure that the pool is healthy and is handling traffic appropriately.4. Communicate your actions to the incident team.

（B）1. Communicate your intent to the incident team.2. Perform a load analysis to determine if the remaining nodes can handle the increase in traffic offloaded from the removed node, and scale appropriately.3. When any new nodes report healthy, drain traffic from the unhealthy node, and remove the unhealthy node from service.

（C）1. Communicate your intent to the incident team.2. Add a new node to the pool, and wait for the new node to report as healthy.3. When traffic is being served on the new node, drain traffic from the unhealthy node, and remove the old node from service.

（D）1 . Drain traffic from the unhealthy node and remove the node from service.2. Monitor traffic to ensure that the error is resolved and that the other nodes in the pool are handling the traffic appropriately.3.
Scale the pool as necessary to handle the new load.4. Communicate your actions to the incident team.