You deploy a new release of an internal application during a weekend maintenance window when there is minimal user tragic. After the window ends, you learn that one of the new features isn't working as expected in the production environment. After an extended outage, you roll back the new release and deploy a fix. You want to modify your release process to reduce the mean time to recovery so you can avoid extended outages in the future. What should you do? (Choose two.)

• A.Before merging new code, require 2 different peers to review the code changes.
• B.Configure a CI server. Add a suite of unit tests to your code and have your CI server run them on commit and verify any changes.
• C.Integrate a code linting tool to validate coding standards before any code is accepted into the repository.
• D.Adopt the blue/green deployment strategy when releasing new code via a CD server.
• E.Require developers to run automated integration tests on their local development environments before release.

Comment: *

Name: *

Email: *

Verification: *

You need to run a business-critical workload on a fixed set of Compute Engine instances for several months.
The workload is stable with the exact amount of resources allocated to it. You want to lower the costs for this workload without any performance implications. What should you do?

• A.Convert the instances to preemptible virtual machines.
• B.Migrate the instances to a Managed Instance Group.
• C.Purchase Committed Use Discounts.
• D.Create an Unmanaged Instance Group for the instances used to run the workload.

Comment: *

Name: *

Email: *

Verification: *

As part of your company's initiative to shift left on security, the infoSec team is asking all teams to implement guard rails on all the Google Kubernetes Engine (GKE) clusters to only allow the deployment of trusted and approved images You need to determine how to satisfy the InfoSec teams goal of shifting left on security.
What should you do?

• A.Deploy Falco or Twistlock on GKE to monitor for vulnerabilities on your running Pods
• B.Configure Identity and Access Management (1AM) policies to create a least privilege model on your GKE clusters
• C.Use Binary Authorization to attest images during your CI CD pipeline
• D.Enable Container Analysis in Artifact Registry, and check for common vulnerabilities and exposures (CVEs) in your container images

Comment: *

Name: *

Email: *

Verification: *

Your application images are built and pushed to Google Container Registry (GCR). You want to build an automated pipeline that deploys the application when the image is updated while minimizing the development effort. What should you do?

• A.Use Cloud Build to trigger a Spinnaker pipeline.
• B.Use a custom builder in Cloud Build to trigger a Jenkins pipeline.
• C.Use Cloud Pub/Sub to trigger a Spinnaker pipeline.
• D.Use Cloud Pub/Sub to trigger a custom deployment service running in Google Kubernetes Engine (GKE).

Comment: *

Name: *

Email: *

Verification: *

You are creating a CI/CD pipeline in Cloud Build to build an application container image The application code is stored in GitHub Your company requires thai production image builds are only run against the main branch and that the change control team approves all pushes to the main branch You want the image build to be as automated as possible What should you do?
Choose 2 answers

• A.Create a trigger on the Cloud Build job Set the repository event setting to Pull request'
• B.Add the owners file to the Included files filter on the trigger
• C.Create a trigger on the Cloud Build job Set the repository event setting to Push to a branch
• D.Configure a branch protection rule for the main branch on the repository
• E.Enable the Approval option on the trigger

Comment: *

Name: *

Email: *

Verification: *