Professional-Cloud-DevOps-Engineer Practice Questions

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.

A.  

Install the Stackdriver Error Reporting library for Python, and then run your code on a Compute Engine VM.

B.  

Install the Stackdriver Error Reporting library for Python, and then run your code on Google Kubernetes Engine.

C.  

Install the Stackdriver Error Reporting library for Python, and then run your code on App Engine flexible environment.

D.  

Use the Stackdriver Error Reporting API to write errors from your application to ReportedErrorEvent, and then generate log entries with properly formatted error messages in Stackdriver Logging.

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 GCL

B.  

D.  

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

A.  

Grant the roles/artifactregistry. writer role to the Cloud Build service account. Confirm that no employee has Artifact Registry write permission.

B.  

Use Cloud Run to write and deploy a custom validator Enable an Eventarc trigger to perform validations when new images are uploaded.

C.  

Configure Kritis to run in your GKE clusters to enforce deploy-time security policies.

D.  

Configure Binary Authorization in your GKE clusters to enforce deploy-time security policies

A.  

Create a Cloud Workstations private cluster. Create a workstation configuration with a runningTimeout parameter.

B.  

Create a Cloud Workstations private cluster. Create a workstation configuration with an idleTimeout parameter.

C.  

Create multiple Compute Engine VM instances with an external IP address and use a Public NAT gateway. Configure an instance schedule to shut down the VMs.

D.  

Create multiple Compute Engine VM instances without an external IP address. Configure an instance schedule to shut down the VMs.

A.  

Import the Stackdriver Profiler package, and configure it to relay function timing data to Stackdriver for further analysis.

B.  

Import the Stackdriver Debugger package, and configure the application to emit debug messages with timing information.

C.  

Instrument the code using a timing library, and publish the metrics via a health check endpoint that is scraped by Stackdriver.

D.  

Install an Application Performance Monitoring (APM) tool in both locations, and configure an export to a central data storage location for analysis.

A.  

Create an attestation for the builds that pass the load test by requiring the lead quality assurance engineer to sign the attestation by using a key stored in Cloud Key Management Service (Cloud KMS).

B.  

Create an attestation for the builds that pass the load test by using a private key stored in Cloud Key Management Service (Cloud KMS) authenticated through Workload Identity.

C.  

Create an attestation for the builds that pass the load test by using a private key stored in Cloud Key Management Service (Cloud KMS) with a service account JSON key stored as a Kubernetes Secret.

D.  

Create an attestation for the builds that pass the load test by requiring the lead quality assurance engineer to sign the attestation by using their personal private key.

A.  

Change the specified SLO to match the measured SLI.

B.  

Move the service to higher-specification compute instances with more memory.

C.  

Set up additional service instances in other zones and load balance the traffic between all instances.

D.  

Set up additional service instances in other zones and use them as a failover in case the primary instance is unavailable.

A.  

Decrease the acknowledgment deadline on the subscription

B.  

Add a virtual queue to the online store that allows typical traffic levels

C.  

Increase the number of Pod replicas

D.  

Increase the Pod CPU and memory limits

A.  

Use custom versions of predefined roles to exclude all iam.serviceAccountKeys. * service account role permissions.

B.  

Apply the constraints/iam.disableserviceAccountKeycreation constraint to the organization.

C.  

Apply the constraints/iam. disableServiceAccountKeyUp10ad constraint to the organization.

D.  

Grant the roles/ iam.serviceAccountKeyAdmin IAM role to organization administrators only.