Free Access Google.Professional-Cloud-DevOps-Engineer.v2026-09-16.q209 Practice Test (Page 38)

Question 181

You are using Terraform to manage infrastructure as code within a Cl/CD pipeline You notice that multiple copies of the entire infrastructure stack exist in your Google Cloud project, and a new copy is created each time a change to the existing infrastructure is made You need to optimize your cloud spend by ensuring that only a single instance of your infrastructure stack exists at a time. You want to follow Google-recommended practices What should you do?

A.Create a new pipeline to delete old infrastructure stacks when they are no longer needed

B.Confirm that the pipeline is storing and retrieving the terraform. if state file from Cloud Storage with the Terraform gcs backend

C.Verify that the pipeline is storing and retrieving the terrafom.tfstat* file from a source control

D.Update the pipeline to remove any existing infrastructure before you apply the latest configuration

Question 182

You are running an application on Compute Engine and collecting logs through Stackdriver. You discover that some personally identifiable information (Pll) is leaking into certain log entry fields. All Pll entries begin with the text userinfo. You want to capture these log entries in a secure location for later review and prevent them from leaking to Stackdriver Logging. What should you do?

A.Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo, and then copy the entries to a Cloud Storage bucket.

B.Create an advanced log filter matching userinfo, configure a log export in the Stackdriver console with Cloud Storage as a sink, and then configure a tog exclusion with userinfo as a filter.

C.Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo, create an advanced log filter matching userinfo, and then configure a log export in the Stackdriver console with Cloud Storage as a sink.

D.Create a basic log filter matching userinfo, and then configure a log export in the Stackdriver console with Cloud Storage as a sink.

Question 183

You are configuring a Cl pipeline. The build step for your Cl pipeline integration testing requires access to APIs inside your private VPC network. Your security team requires that you do not expose API traffic publicly. You need to implement a solution that minimizes management overhead. What should you do?

A.Use Spinnaker for Google Cloud to connect to the private VPC.

B.Use Cloud Build as a pipeline runner. Configure Internal HTTP(S) Load Balancing for API access.

C.Use Cloud Build as a pipeline runner. Configure External HTTP(S) Load Balancing with a Google Cloud Armor policy for API access.

D.Use Cloud Build private pools to connect to the private VPC.

Question 184

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.

D.use the Terraform module so that Secret Manager can retrieve credentials.

Correct Answer: 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.

Question 185

You are on-call for an infrastructure service that has a large number of dependent systems. You receive an alert indicating that the service is failing to serve most of its requests and all of its dependent systems with hundreds of thousands of users are affected. As part of your Site Reliability Engineering (SRE) incident management protocol, you declare yourself Incident Commander (IC) and pull in two experienced people from your team as Operations Lead (OLJ and Communications Lead (CL). What should you do next?

A.Look for ways to mitigate user impact and deploy the mitigations to production.

B.Contact the affected service owners and update them on the status of the incident.

C.Establish a communication channel where incident responders and leads can communicate with each other.

D.Start a postmortem, add incident information, circulate the draft internally, and ask internal stakeholders for input.

Other Version: 983Google.Professional-Cloud-DevOps-Engineer.v2026-03-30.q189; 2958Google.Professional-Cloud-DevOps-Engineer.v2025-09-27.q141; 1261Google.Professional-Cloud-DevOps-Engineer.v2023-01-21.q29; 2522Google.Professional-Cloud-DevOps-Engineer.v2022-06-30.q61; 2690Google.Professional-Cloud-DevOps-Engineer.v2022-04-13.q62; 65Google.Pass4surecert.Professional-Cloud-DevOps-Engineer.v2021-09-22.by.horace.37q.pdf

Latest Upload: 164Google.Professional-Cloud-DevOps-Engineer.v2026-09-16.q209; 148AAPC.CPC.v2026-09-16.q132; 116HP.HPE0-J82.v2026-09-16.q26; 178F5.303.v2026-09-16.q147; 169PaloAltoNetworks.NGFW-Engineer.v2026-09-16.q105; 127Workday.Workday-Pro-Recruiting.v2026-09-15.q19; 141ACAMS.CAMS-FCI.v2026-09-15.q36; 157VMware.250-614.v2026-09-15.q42; 184IAPP.CIPM.v2026-09-15.q217; 170VMware.2V0-13.25.v2026-09-14.q122

Question 181

Question 182

Question 183

Question 184

Question 185

Download PDF File