Question 1

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 Kubernetes Engine Enterprise (GKE Enterprise) cluster created so that application teams can deploy their applications. Config Sync will be used and templated to deploy infrastructure-level resources in each GKE Enterprise 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 (IaC) and application code?

Options :

A : Cloud Infrastructure (Terraform) repository is shared: different directories are different environments GKE Enterprise Infrastructure (Config Sync 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 Enterprise Infrastructure (Config Sync 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 Enterprise Infrastructure (Config Sync 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 Enterprise Infrastructure (Config Sync Kustomize manifests) repositories are separated: different overlay directories are different environments Application (app source code) repositories are separated: different branches are different features

Answer: A

Question 2

As a member of an organization that adheres to SRE practices and principles, you have taken over the management of a new service from the Development Team. To ensure that the service meets its Service Level Objectives (SLOs) in production, you conducted a Production Readiness Review (PRR) and found that the service is currently unable to meet its SLOs. Your goal is to ensure that the service is able to meet its SLOs in production.What is the next step you should take?

Options :

A : Adjust the SLO targets to be achievable by the service so you can bring it into production.

B : Notify the development team that they will have to provide production support for the service.

C : Identify recommended reliability improvements to the service to be completed before handover.

D : Bring the service into production with no SLOs and build them when operational data is collected.

Answer: C

Question 3

The NGINX-based application was recently deployed by your team on Google Kubernetes Engine (GKE) and exposed to the public through an HTTP Google Cloud Load Balancer (GCLB) ingress. You intend to increase the frontend deployment of the application using a suitable Service Level Indicator (SLI).What actions do you need to take?

Options :

A : Configure the horizontal pod autoscaler to use the average response time from the Liveness and Readiness probes.

B : Configure the vertical pod autoscaler in GKE and enable the cluster autoscaler to scale the cluster as pods expand.

C : Install the Stackdriver custom metrics adapter and configure a horizontal pod autoscaler to use the number of requests provided by the GCLB.

D : Expose the NGINX stats endpoint and configure the horizontal pod autoscaler to use the request metrics exposed by the NGINX deployment.

Answer: C

Question 4

What is an important feature that a monitoring system should have for displaying time series data?

Options :

A : Only displaying data in one format

B : No option to aggregate information

C : No configurable options

D : Capabilities to display data in different formats

Answer: D

Question 5

The deployment of a new feature for a web-based application to production is imminent, and Google Kubernetes Engine (GKE) will be used to perform a phased rollout to half of the web server pods.What actions do you think would be appropriate?

Options :

A : Use a partitioned rolling update.

B : Use Node taints with NoExecute.

C : Use a replica set in the deployment specification.

D : Use a stateful set with parallel pod management policy.

Answer: A

Free Professional-Cloud-DevOps-Engineer Mock Exam – Practice Online Confidently

Buying Options: