Professional-Cloud-DevOps-Engineer Practice Exam Questions and Answers

A.  

Use the --cache-from parameter, and point to Artifact Registry. Add the most frequently modified files to the later stages of the build process.

B.  

Use the --cache-from parameter, and point to Artifact Registry. Add the most frequently modified files to the earlier stages of the build process.

C.  

Cache the container layers of the build process to Cloud Storage. Add the most frequently modified files to the earlier stages of the build process.

D.  

Cache the container layers of the build process to Cloud Storage. Add the most frequently modified files to the later stages of the build process.

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 you have collected operational data.

A.  

Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.

B.  

Look through other metrics related to the product and find SLOs with remaining error budget. Reallocate the error budgets and allow the feature launch.

C.  

Escalate the situation and request additional error budget.

D.  

Notify the team about the lack of error budget and ensure that all their tests are successful so the launch will not further risk the error budget.

A.  

Create SLIs from metrics Enable Alert Policies if the services do not pass

B.  

Use the metrics from Anthos Service Mesh to measure the health of the microservices

C.  

Create a SLO Create an Alert Policy on select_slo_bum_rate

D.  

Create a SLO and configure uptime checks for your services Enable Alert Policies if the services do not pass

A.  

Disable the CI pipeline and revert to manually building and pushing the artifacts.

B.  

Change the CI pipeline to push the artifacts to Container Registry instead of Docker Hub.

C.  

Upload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix the issue.

D.  

Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.

A.  

Select a latency metric for a request-based method of evaluation.

B.  

Select a latency metric for a window-based method of evaluation.

C.  

Select an availability metric for a request-based method of evaluation.

D.  

Select an availability metric for a window-based method Of evaluation.

A.  

Add high memory compute nodes to the cluster.

B.  

Increase the memory limit in the application deployment.

C.  

Add Cloud Trace to the application, and redeploy.

D.  

Increase the CPU limit in the application deployment.

A.  

Configure the VPC as a Shared VPC Host project.

B.  

Configure your network services on the Standard Tier.

C.  

Configure your Kubernetes duster as a Private Cluster.

D.  

Configure a Google Cloud HTTP Load Balancer as Ingress.

A.  

Create an organization-level aggregated sink with a SIEM Pub/Sub topic as the destination. Set an inclusion filter to include all logs.

B.  

Create a project-level logging sink with a SIEM Pub/Sub topic as the destination. Set an inclusion filter to include all logs. Repeat for each project.

C.  

Create an organization-level aggregated sink with a SIEM log bucket as the destination. Set an inclusion filter to include all logs.

D.  

Create a folder-level aggregated sink with a SIEM Pub/Sub topic as the destination. Set an inclusion filter to include all logs. Repeat for each folder.

A.  

1. Communicate your intent to the incident team.2. Perform a load analysis to determine if the remaining nodes can handle the increase in traffic offloaded from the removed node, and scale appropriately.3. When any new nodes report healthy, drain traffic from the unhealthy node, and remove the unhealthy node from service.

B.  

1. Communicate your intent to the incident team.2. Add a new node to the pool, and wait for the new node to report as healthy.3. When traffic is being served on the new node, drain traffic from the unhealthy node, and remove the old node from service.

C.  

1 . Drain traffic from the unhealthy node and remove the node from service.2. Monitor traffic to ensure that the error is resolved and that the other nodes in the pool are handling the traffic appropriately.3. Scale the pool as necessary to handle the new load.4. Communicate your actions to the incident team.

D.  

1 . Drain traffic from the unhealthy node and remove the old node from service.2. Add a new node to the pool, wait for the new node to report as healthy, and then serve traffic to the new node.3. Monitor traffic to ensure that the pool is healthy and is handling traffic appropriately.4. Communicate your actions to the incident team.