You are configuring your CI/CD pipeline natively on Google Cloud. You want builds in a pre-production Google Kubernetes Engine (GKE) environment to be automatically load-tested before being promoted to the production GKE environment. You need to ensure that only builds that have passed this test are deployed to production. You want to follow Google-recommended practices. How should you configure this pipeline with Binary Authorization?

• 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.

Comment: *

Name: *

Email: *

Verification: *

You have a pool of application servers running on Compute Engine. You need to provide a secure solution that requires the least amount of configuration and allows developers to easily access application logs for troubleshooting. How would you implement the solution on GCP?

• A.* Deploy the Stackdriver monitoring agent to the application servers.
  * Give the developers the IAM Monitoring Viewer role to access Stackdriver and view metrics.
• B.* Deploy the Stackdriver logging agent to the application servers.
  * Give the developers the IAM Logs Private Logs Viewer role to access Stackdriver and view logs.
• C.* Install the gsutil command line tool on your application servers.
  * Write a script using gsutil to upload your application log to a Cloud Storage bucket, and then schedule it to run via cron every 5 minutes.
  * Give the developers the IAM Object Viewer access to view the logs in the specified bucket.
• D.* Deploy the Stackdriver logging agent to the application servers.
  * Give the developers the IAM Logs Viewer role to access Stackdriver and view logs.

Comment: *

Name: *

Email: *

Verification: *

You are running an experiment to see whether your users like a new feature of a web application. Shortly after deploying the feature as a canary release, you receive a spike in the number of 500 errors sent to users, and your monitoring reports show increased latency. You want to quickly minimize the negative impact on users.
What should you do first?

• A.Start monitoring latency, traffic, errors, and saturation.
• B.Record data for the postmortem document of the incident.
• C.Trace the origin of 500 errors and the root cause of increased latency.
• D.Roll back the experimental canary release.

Comment: *

Name: *

Email: *

Verification: *

You currently store the virtual machine (VM) utilization logs in Stackdriver. You need to provide an easy-to-share interactive VM utilization dashboard that is updated in real time and contains information aggregated on a quarterly basis. You want to use Google Cloud Platform solutions. What should you do?

• A.1. Export VM utilization logs from Stackdriver to Cloud Pub/Sub.
  2. From Cloud Pub/Sub, send the logs to a Security Information and Event Management (SIEM) system.
  3. Build the dashboards in the SIEM system and share with your stakeholders.
• B.1. Export VM utilization logs from Stackdriver to BigOuery.
  2. Create a dashboard in Data Studio.
  3. Share the dashboard with your stakeholders.
• C.1. Export VM utilization logs (rom Stackdriver to BigQuery.
  2. From BigQuery. export the logs to a CSV file.
  3. Import the CSV file into Google Sheets.
  4. Build a dashboard in Google Sheets and share it with your stakeholders.
• D.1. Export VM utilization logs from Stackdriver to a Cloud Storage bucket.
  2. Enable the Cloud Storage API to pull the logs programmatically.
  3. Build a custom data visualization application.
  4. Display the pulled logs in a custom dashboard.

Comment: *

Name: *

Email: *

Verification: *

You are building the Cl/CD pipeline for an application deployed to Google Kubernetes Engine (GKE) The application is deployed by using a Kubernetes Deployment, Service, and Ingress The application team asked you to deploy the application by using the blue'green deployment methodology You need to implement the rollback actions What should you do?

• A.Run the kubectl rollout undo command
• B.Delete the new container image, and delete the running Pods
• C.Update the Kubernetes Service to point to the previous Kubernetes Deployment
• D.Scale the new Kubernetes Deployment to zero

Comment: *

Name: *

Email: *

Verification: *