Free Access to Google.Professional-Cloud-DevOps-Engineer.v2024-08-12.q133 with Valid Practice Test (Page 9)

Question 36

You are designing a system with three different environments: development, quality assurance (QA), and production.
Each environment will be deployed with Terraform and has a Google Kubemetes Engine (GKE) cluster created so that application teams can deploy their applications. Anthos Config Management will be used and templated to deploy infrastructure level resources in each GKE cluster. All users (for example, infrastructure operators and application owners) will use GitOps. How should you structure your source control repositories for both Infrastructure as Code (laC) and application code?

A.Cloud Infrastructure (Terraform) repository is shared: different directories are different environments GKE Infrastructure (Anthos Config Management Kustomize manifests) repository is shared: different overlay directories are different environments Application (app source code) repositories are separated:
different branches are different features
B.Cloud Infrastructure (Terraform) repository is shared: different directories are different environments GKE Infrastructure (Anthos Config Management Kustomize manifests) repositories are separated:
different branches are different environments Application (app source code) repositories are separated:
different branches are different features
C.Cloud Infrastructure (Terraform) repository is shared: different branches are different environments GKE Infrastructure (Anthos Config Management Kustomize manifests) repository is shared: different overlay directories are different environments Application (app source code) repository is shared:
different directories are different features
D.Cloud Infrastructure (Terraform) repositories are separated: different branches are different environments GKE Infrastructure (Anthos Config Management Kustomize manifests) repositories are separated: different overlay directories are different environments Application (app source code) repositories are separated: different branches are different features

Correct Answer: B

Explanation
The correct answer is B. Cloud Infrastructure (Terraform) repository is shared: different directories are different environments. GKE Infrastructure (Anthos Config Management Kustomize manifests) repositories are separated: different branches are different environments. Application (app source code) repositories are separated: different branches are different features.
This answer follows the best practices for using Terraform and Anthos Config Management with GitOps, as described in the following sources:
For Terraform, it is recommended to use a single repository for all environments, and use directories to separate them. This way, you can reuse the same Terraform modules and configurations across environments, and avoid code duplication and drift. You can also use Terraform workspaces to isolate the state files for each environment12.
For Anthos Config Management, it is recommended to use separate repositories for each environment, and use branches to separate the clusters within each environment. This way, you can enforce different policies and configurations for each environment, and use pull requests to promote changes across environments. You can also use Kustomize to create overlays for each cluster that apply specific patches or customizations34.
For application code, it is recommended to use separate repositories for each application, and use branches to separate the features or bug fixes for each application. This way, you can isolate the development and testing of each application, and use pull requests to merge changes into the main branch. You can also use tags or labels to trigger deployments to different environments5 .
References:
1: Best practices for using Terraform | Google Cloud
2: Terraform Recommended Practices - Part 1 | Terraform - HashiCorp Learn
3: Deploy Anthos on GKE with Terraform part 1: GitOps with Config Sync | Google Cloud Blog
4: Using Kustomize with Anthos Config Management | Anthos Config Management Documentation | Google Cloud
5: Deploy Anthos on GKE with Terraform part 3: Continuous Delivery with Cloud Build | Google Cloud Blog GitOps-style continuous delivery with Cloud Build | Cloud Build Documentation | Google Cloud

Question 37

You support a popular mobile game application deployed on Google Kubernetes Engine (GKE) across several Google Cloud regions. Each region has multiple Kubernetes clusters. You receive a report that none of the users in a specific region can connect to the application. You want to resolve the incident while following Site Reliability Engineering practices. What should you do first?

A.Reroute the user traffic from the affected region to other regions that don't report issues.
B.Use Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.
C.Add an extra node pool that consists of high memory and high CPU machine type instances to the cluster.
D.Use Stackdriver Logging to filter on the clusters in the affected region, and inspect error messages in the logs.

Question 38

You are running a web application deployed to a Compute Engine managed instance group Ops Agent is installed on all instances You recently noticed suspicious activity from a specific IP address You need to configure Cloud Monitoring to view the number of requests from that specific IP address with minimal operational overhead. What should you do?

A.Configure the Ops Agent with a logging receiver Create a logs-based metric
B.Create a script to scrape the web server log Export the IP address request metrics to the Cloud Monitoring API
C.Update the application to export the IP address request metrics to the Cloud Monitoring API
D.Configure the Ops Agent with a metrics receiver

Question 39

You use Cloud Build to build your application. You want to reduce the build time while minimizing cost and development effort. What should you do?

A.Use Cloud Storage to cache intermediate artifacts.
B.Use larger Cloud Build virtual machines (VMs) by using the machine-type option.
C.Run multiple Jenkins agents to parallelize the build.
D.Use multiple smaller build steps to minimize execution time.

Question 40

You support a service that recently had an outage. The outage was caused by a new release that exhausted the service memory resources. You rolled back the release successfully to mitigate the impact on users. You are now in charge of the post-mortem for the outage. You want to follow Site Reliability Engineering practices when developing the post-mortem. What should you do?

A.Focus on identifying the contributing causes of the incident rather than the individual responsible for the cause.
B.Use the Git history to find the related code commit. Prevent the engineer who made that commit from working on production services.
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.

Question 36

Question 37

Question 38

Question 39

Question 40

Download PDF File