Free Google Professional-Cloud-DevOps-Engineer Exam Questions

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?

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

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?

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 3

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?

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 4

What is the definition of SLI in the context of SRE terminology?

A : The expectation that a service is available or reliable for a certain target level over a specific period

B : Expecting the service to be available or expecting the service to meet a specific amount of latency, throughput, or freshness, or any other characteristic that is critical to the user journey

C : The expectation that a service will meet a pre-defined customer expectation, the failure of which results in a refund or credits

D : The ability of an application or service to perform a specific function within a specific time without failures

Answer: B

Question 5

Service Level Objectives (SLOs) must be established for a multi-region web application that receives high traffic. The customers anticipate the application to maintain high availability and provide prompt response times. At present, the customers are satisfied with the application's performance and availability. The current measurements show that the 90th percentile of latency is 120ms, and the 95th percentile of latency is 275ms over a 28-day period.

What would be your recommended latency SLO for the team to meet before publishing?

A : 90 percentile '"" 100ms th 95 percentile '"" 250ms th

B : 90 percentile '"" 120ms th 95 percentile '"" 275ms th

C : 90 percentile '"" 150ms th 95 percentile '"" 300ms th

D : 90 percentile '"" 250ms th 95 percentile '"" 400ms th

Answer: C