Professional-Cloud-DevOps-Engineer Practice Test

Your application services run in Google Kubernetes Engine (GKE). You want to make sure that only images from your centrally-managed Google Container Registry (GCR) image registry in the altostrat-images project can be deployed to the cluster while minimizing development time. What should you do?

A.

Create a custom builder for Cloud Build that will only push images to gcr.io/altostratimages.

B.

Use a Binary Authorization policy that includes the whitelist name pattern
gcr.io/attostrat-images/.

C.

Add logic to the deployment pipeline to check that all manifests contain only images from gcr.io/altostrat-images.

D.

Add a tag to each image in gcr.io/altostrat-images and check that this tag is present when the image is deployed.

You support a high-traffic web application with a microservice architecture. The home page
of the application displays multiple widgets containing content such as the current weather,
stock prices, and news headlines. The main serving thread makes a call to a dedicated
microservice for each widget and then lays out the homepage for the user. The
microservices occasionally fail; when that happens, the serving thread serves the
homepage with some missing content. Users of the application are unhappy if this
degraded mode occurs too frequently, but they would rather have some content served
instead of no content at all. You want to set a Service Level Objective (SLO) to ensure that
the user experience does not degrade too much. What Service Level Indicator {SLI) should
you use to measure this?

A.

A quality SLI: the ratio of non-degraded responses to total responses

B.

An availability SLI: the ratio of healthy microservices to the total number of
microservices

C.

A freshness SLI: the proportion of widgets that have been updated within the last 10 minutes

D.

A latency SLI: the ratio of microservice calls that complete in under 100 ms to the total number of microservice calls

You use Cloud Build to build and deploy your application. You want to securely incorporate database credentials and other application secrets into the build pipeline. You also want to minimize the development effort. What should you do?

A.

Create a Cloud Storage bucket and use the built-in encryption at rest. Store the secrets in the bucket and grant Cloud Build access to the bucket.

B.

Encrypt the secrets and store them in the application repository. Store a decryption key
in a separate repository and grant Cloud Build access to the repository.

C.

Use client-side encryption to encrypt the secrets and store them in a Cloud Storage bucket. Store a decryption key in the bucket and grant Cloud Build access to the bucket.

D.

Use Cloud Key Management Service (Cloud KMS) to encrypt the secrets and include
them in your Cloud Build deployment configuration. Grant Cloud Build access to the
KeyRing.

You are running an application in a virtual machine (VM) using a custom Debian image. The image has the Stackdriver Logging agent installed. The VM has the cloud-platform scope. The application is logging information via syslog. You want to use Stackdriver Logging in the Google Cloud Platform Console to visualize the logs. You notice that syslog is not showing up in the "All logs" dropdown list of the Logs Viewer. What is the first thing you should do?

A.

Look for the agent's test log entry in the Logs Viewer.

B.

Install the most recent version of the Stackdriver agent.

C.

Verify the VM service account access scope includes the monitoring.write scope.

D.

SSH to the VM and execute the following commands on your VM: ps ax I grep fluentd

Your team has recently deployed an NGINX-based application into Google Kubernetes Engine (GKE) and has exposed it to the public via an HTTP Google Cloud Load Balancer (GCLB) ingress. You want to scale the deployment of the application's frontend using an appropriate Service Level Indicator (SLI). What should you do?

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.