You are building and deploying a microservice on Cloud Run for your organization Your service is used by many applications internally You are deploying a new release, and you need to test the new version extensively in the staging and production environments You must minimize user and developer impact. What should you do?

• A.Deploy the new version of the service to the staging environment Split the traffic, and allow 1 % of traffic through to the latest version Test the latest version If the test passes gradually roll out the latest version to the staging and production environments
• B.Deploy the new version of the service to the staging environment Split the traffic, and allow 50% of traffic through to the latest version Test the latest version If the test passes, send all traffic to the latest version Repeat for the production environment
• C.Deploy the new version of the service to the staging environment with a new-release tag without serving traffic Test the new-release version If the test passes; gradually roll out this tagged version Repeat for the production environment
• D.Deploy a new environment with the green tag to use as the staging environment Deploy the new version of the service to the green environment and test the new version If the tests pass, send all traffic to the green environment and delete the existing staging environment Repeat for the production environment

Comment: *

Name: *

Email: *

Verification: *

You want to share a Cloud Monitoring custom dashboard with a partner team What should you do?

• A.Provide the partner team with the dashboard URL to enable the partner team to create a copy of the dashboard
• B.Export the metrics to BigQuery Use Looker Studio to create a dashboard, and share the dashboard with the partner team
• C.Copy the Monitoring Query Language (MQL) query from the dashboard; and send the MQL query to the partner team
• D.Download the JSON definition of the dashboard, and send the JSON file to the partner team

Comment: *

Name: *

Email: *

Verification: *

You are running a real-time gaming application on Compute Engine that has a production and testing environment. Each environment has their own Virtual Private Cloud (VPC) network. The application frontend and backend servers are located on different subnets in the environment's VPC. You suspect there is a malicious process communicating intermittently in your production frontend servers. You want to ensure that network traffic is captured for analysis. What should you do?

• A.Enable VPC Flow Logs on the production VPC network frontend and backend subnets only with a sample volume scale of 0.5.
• B.Enable VPC Flow Logs on the testing and production VPC network frontend and backend subnets with a volume scale of 0.5. Apply changes in testing before production.
• C.Enable VPC Flow Logs on the production VPC network frontend and backend subnets only with a sample volume scale of 1.0.
• D.Enable VPC Flow Logs on the testing and production VPC network frontend and backend subnets with a volume scale of 1.0. Apply changes in testing before production.

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.Record data for the postmortem document of the incident.
• B.Roll back the experimental canary release.
• C.Trace the origin of 500 errors and the root cause of increased latency.
• D.Start monitoring latency, traffic, errors, and saturation.

Comment: *

Name: *

Email: *

Verification: *

Your company follows Site Reliability Engineering practices. You are the person in charge of Communications for a large, ongoing incident affecting your customer-facing applications. There is still no estimated time for a resolution of the outage. You are receiving emails from internal stakeholders who want updates on the outage, as well as emails from customers who want to know what is happening. You want to efficiently provide updates to everyone affected by the outage. What should you do?

• A.Delegate the responding to internal stakeholder emails to another member of the Incident Response Team. Focus on providing responses directly to customers.
• B.Provide all internal stakeholder emails to the Incident Commander, and allow them to manage internal communications. Focus on providing responses directly to customers.
• C.Provide periodic updates to all stakeholders in a timely manner. Commit to a "next update" time in all communications.
• D.Focus on responding to internal stakeholders at least every 30 minutes. Commit to "next update" times.

Comment: *

Name: *

Email: *

Verification: *