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

You need to tackle the root causes of an outage that has already occurred, and to do so, you are creating and assigning action items in a postmodern. Your goal is to make sure that your team handles these action items with speed and efficiency.What is the recommended approach for assigning owners and collaborators to action items?

Options :

A : Assign multiple owners for each item to guarantee that the team addresses items quickly.

B : Assign the team lead as the owner for all action items because they are in charge of the SRE team.

C : Assign one owner for each action item and any necessary collaborators.

D : Assign collaborators but no individual owners to the items to keep the postmortem blameless.

Answer: C

Question 3

What is one of the key factors to consider when implementing the on call process?

Options :

A : The size of the SRE team

B : The type of service being supported

C : The location of the data center

D : Paging versus non-paging events

Answer: D

Question 4

What are common means of notification when alerting rules are violated?

Options :

A : A push notification

B : A social media post

C : An email, a page, or a ticket

D : A phone call

Answer: C

Question 5

What is a sidecar pattern in Kubernetes?

Options :

A : A type of Pod with multiple containers where one container supports the main application container

B : A type of Pod that runs only one container

C : A type of Pod with multiple containers that share the same resources

D : A type of Pod with multiple containers that run independently

Answer: A

Confidently Practice Online with Free Professional-Cloud-DevOps-Engineer Exam Cram

Buying Options: