Question 1

Your application is deployed across several Google Kubernetes Engine clusters, with each cluster managed by a Deployment. The Deployment has generated several replicas of your Pod in every cluster. You intend to access the logs sent to stdout for all the replicas in your Deployment across all clusters.

What is the appropriate command to use?

Options :

A : kubectl logs [PARAM]

B : gcloud logging read [PARAM]

C : kubectl exec ""it [PARAM] journalctl

D : gcloud compute ssh [PARAM] ""-command= 'sudo journalctl'

Answer: B

Question 2

You work at a rapidly growing financial technology startup. You manage the payment processing application

written in Go and hosted on Cloud Run in the Singapore region (asia-southeast1). The payment processing

application processes data stored in a Cloud Storage bucket that is also located in the Singapore region.

The startup plans to expand further into the Asia Pacific region. You plan to deploy the Payment Gateway in

Jakarta, Hong Kong, and Taiwan over the next six months. Each location has data residency requirements that

require customer data to reside in the country where the transaction was made. You want to minimize the cost

of these deployments. What should you do?

Options :

A : Create a Cloud Storage bucket in each region, and create a Cloud Run service of the payment processing application in each region

B : Create a Cloud Storage bucket in each region, and create three Cloud Run services of the payment processing application in the Singapore region.

C : Create three Cloud Storage buckets in the Asia multi-region, and create three Cloud Run services of the payment processing application in the Singapore region

D : Create three Cloud Storage buckets in the Asia multi-region, and create three Cloud Run revisions of the payment processing application in the Singapore region.

Answer: A

Question 3

A CI/CD pipeline is being developed, which includes a version control system, Cloud Build, and Container Registry. Whenever a new tag is added to the repository, a Cloud Build job is activated. This job performs unit tests on the latest code, creates a new Docker container image, and saves it to the Container Registry. The final phase of the pipeline is to deploy the updated container to the production Google Kubernetes Engine (GKE) cluster.

What options are available to choose a tool and deployment strategy that satisfies these conditions:

• No downtime should be experienced

• Automated testing should be comprehensive

• Testing before release should be possible

• Quick rollbacks should be supported

Options :

A : Trigger a Spinnaker pipeline configured as an A/B test of your new code and, if successful, deploy the container to production.

B : Trigger a Cloud Build job that utilizes Kubernetes CLI tools to deploy your new container to your GKE cluster, allowing for a canary test.

C : Trigger a Cloud Build job that utilizes Kubernetes CLI tools to deploy your new container to your GKE cluster, allowing for a shadow test.

D : Trigger a Spinnaker pipeline configured as a canary test of your new code and, if successful, deploy the container to production.

Answer: C

Question 4

You are developing an application that consists of several microservices running in a Google Kubernetes Engine cluster. One microservice needs to connect to a third-party database running on-premises. You need to store credentials to the database and ensure that these credentials can be rotated while following security best practices. What should you do?

Options :

A : Store the credentials in a sidecar container proxy. and use it to connect to the third-party database.

B : Configure a service mesh to allow or restrict traffic from the Pods in your microservice to the database.

C : Store the credentials in an encrypted volume mount, and associate a Persistent Volume Claim with the client Pod.

D :

Store the credentials as a Kubemetes Secret, and use the Cloud Key Management Service plugin to handle encryption and decryption

Answer: A

Question 5

Working alongside the CI/CD team, you, as a developer, are tasked with identifying and resolving a problem that has arisen with a new feature that your team has recently introduced. The CI/CD team employed HashiCorp Packer to generate a fresh Compute Engine image from your development branch, which proved successful in its creation. However, the image is currently unable to start up and requires investigation by the CI/CD team.

What actions are recommended?

Options :

A : Install Packer on your device, build the Compute Engine image locally, and then run it in your personal Google Cloud project.

B : Verify the Compute Engine OS logs through the serial port and confirm access to the serial port by checking the Cloud Logging logs.

C : Create a new feature branch and request the build team to reconstruct the image.

D : Power off the virtual machine in use, export the disk, and mount it locally to access the boot logs.

Answer: B