Google Professional Cloud DevOps Engineer Exam Questions Instant Access

Question 1

You use Terraform to manage an application deployed to a Google Cloud environment The application runs on instances deployed by a managed instance group The Terraform code is deployed by using aCI/CD pipeline When you change the machine type on the instance template used by the managed instance group, the pipeline fails at the terraform apply stage with the following error message

You need to update the instance template and minimize disruption to the application and the number of pipeline runs What should you do?

ADelete the managed instance group and recreate it after updating the instance template

BAdd a new instance template update the managed instance group to use the new instance template and delete the old instance template

CRemove the managed instance group from the Terraform state file update the instance template and reimport the managed instance group.

DSet the create_bef ore_destroy meta-argument to true in the lifecycle block on the instance template

Answer : D

The best option for updating the instance template and minimizing disruption to the application and the number of pipeline runs is to set the create_before_destroy meta-argument to true in the lifecycle block on the instance template. The create_before_destroy meta-argument is a Terraform feature that specifies that a new resource should be created before destroying an existing one during an update. This way, you can avoid downtime and errors when updating a resource that is in use by another resource, such as an instance template that is used by a managed instance group. By setting the create_before_destroy meta-argument to true in the lifecycle block on the instance template, you can ensure that Terraform creates a new instance template with the updated machine type, updates the managed instance group to use the new instance template, and then deletes the old instance template.

Question 2

Your development team has created a new version of their service's API. You need to deploy the new versions of the API with the least disruption to third-party developers and end users of third-party installed applications. What should you do?

AIntroduce the new version of the API.Announce deprecation of the old version of the API.Deprecate the old version of the API.Contact remaining users of the old API.Provide best effort support to users of the old API.Turn down the old version of the API.

BAnnounce deprecation of the old version of the API.Introduce the new version of the API.Contact remaining users on the old API.Deprecate the old version of the API.Turn down the old version of the API.Provide best effort support to users of the old API.

CAnnounce deprecation of the old version of the API.Contact remaining users on the old API.Introduce the new version of the API.Deprecate the old version of the API.Provide best effort support to users of the old API.Turn down the old version of the API.

DIntroduce the new version of the API.Contact remaining users of the old API.Announce deprecation of the old version of the API.Deprecate the old version of the API.Turn down the old version of the API.Provide best effort support to users of the old API.

Answer : A

Question 3

You support a large service with a well-defined Service Level Objective (SLO). The development team deploys new releases of the service multiple times a week. If a major incident causes the service to miss its SLO, you want the development team to shift its focus from working on features to improving service reliability. What should you do before a major incident occurs?

ADevelop an appropriate error budget policy in cooperation with all service stakeholders.

BNegotiate with the product team to always prioritize service reliability over releasing new features.

CNegotiate with the development team to reduce the release frequency to no more than once a week.

DAdd a plugin to your Jenkins pipeline that prevents new releases whenever your service is out of SLO.

Answer : A

Reason : Incident has not occurred yet, even when development team is already pushing new features multiple times a week. The option A says, to define an error budget 'policy', not to define error budget(It is already present). Just simple means to bring in all stakeholders, and decide how to consume the error budget effectively that could bring balance between feature deployment and reliability.

The goals of this policy are to: -- Protect customers from repeated SLO misses -- Provide an incentive to balance reliability with other featureshttps://sre.google/workbook/error-budget-policy/

Question 4

You are managing an MLOps platform on a Google Kubernetes Engine (GKE) cluster that serves two teams:

The Research team runs hundreds of small, daily experiments that can run as capacity allows and are highly cost-sensitive.

The Production team must retrain the company's main language model every Friday at 10:00 PM. This job is business-critical, cannot be interrupted, and must start on time.

You need to configure the modes for Dynamic Workload Scheduler to meet each team's requirements. What should you do?

AUse Flex Start mode for both the Research and Production teams.

BUse Flex Start mode for the Research team and Calendar mode for the Production team.

CUse Calendar mode for both the Research and Production teams.

DUse Calendar mode for the Research team and Flex Start mode for the Production team.

Answer : B

Comprehensive and Detailed 150 to 200 words of Explanation From Google Cloud DevOps guides documents:

Google Cloud's Dynamic Workload Scheduler offers two distinct modes designed to balance resource availability with cost and criticality. Flex Start mode is optimized for cost-sensitive, asynchronous workloads that do not have a strict start time. It allows the scheduler to obtain capacity when it becomes available within a 7-day window, making it the ideal choice for the Research team's hundreds of small experiments. This mode prioritizes resource optimization and lower costs over immediate execution.

Conversely, Calendar mode is designed for business-critical jobs that require guaranteed capacity at a specific date and time. By using Calendar mode, the Production team can reserve the necessary GPU or TPU resources for their Friday 10:00 PM retraining session. This ensures the job starts exactly on time and runs without interruption, satisfying the 'business-critical' requirement. Combining these two modes allows an organization to maximize cluster utilization: using Flex Start to fill the gaps with non-urgent research while ensuring that high-priority production tasks have the 'just-in-time' resource guarantees they need to maintain SLOs (Service Level Objectives).

Question 5

You recently deployed your application in Google Kubernetes Engine (GKE) and now need to release a new version of the application You need the ability to instantly roll back to the previous version of the application in case there are issues with the new version Which deployment model should you use?

APerform a rolling deployment and test your new application after the deployment is complete

BPerform A. B testing, and test your application periodically after the deployment is complete

CPerform a canary deployment, and test your new application periodically after the new version is deployed

DPerform a blue/green deployment and test your new application after the deployment is complete

Answer : D

The best deployment model for releasing a new version of your application in GKE with the ability to instantly roll back to the previous version is to perform a blue/green deployment and test your new application after the deployment is complete. A blue/green deployment is a deployment strategy that involves creating two identical environments, one running the current version of the application (blue) and one running the new version of the application (green). The traffic is switched from blue to green after testing the new version, and if any issues are discovered, the traffic can be switched back to blue instantly. This way, you can minimize downtime and risk during deployment.

Question 6

You are investigating issues in your production application that runs on Google Kubernetes Engine (GKE). You determined that the source Of the issue is a recently updated container image, although the exact change in code was not identified. The deployment is currently pointing to the latest tag. You need to update your cluster to run a version of the container that functions as intended. What should you do?

ACreate a new tag called stable that points to the previously working container, and change the deployment to point to the new tag.

BApply the latest tag to the previous container image, and do a rolling update on the deployment.

CBuild a new container from a previous Git tag, and do a rolling update on the deployment to the new container.

DAlter the deployment to point to the sha2 56 digest of the previously working container.

Answer : D

Question 7

You are developing a Node.js utility on a workstation in Cloud Workstations by using Code OSS. The utility is a simple web page, and you have already confirmed that all necessary firewall rules are in place. You tested the application by starting it on port 3000 on your workstation in Cloud Workstations, but you need to be able to access the web page from your local machine. You need to follow Google-recommended security practices. What should you do?

AAllow public IP addresses in the Cloud Workstations configuration.

BUse a browser running on a bastion host VM.

CRun the gcloud compute start-iap-tunnel command to the Cloud Workstations VM.

DClick the preview link in the Code OSS panel.

Answer : D

Cloud Workstations provides a secure way to preview web applications using built-in preview links, which expose internal ports only via authenticated and authorized access --- no public IP exposure required.

''To preview your app, click the preview icon in the Code OSS panel, which securely tunnels the service to your browser.''

--- Cloud Workstations - Previewing your app

This adheres to Google's security best practices by avoiding public IPs or manual tunneling while enabling developer efficiency.