You support a web application that runs on App Engine and uses CloudSQL and Cloud Storage for data storage. After a short spike in website traffic, you notice a big increase in latency for all user requests, increase in CPU use, and the number of processes running the application. Initial troubleshooting reveals:
After the initial spike in traffic, load levels returned to normal but users still experience high latency.
Requests for content from the CloudSQL database and images from Cloud Storage show the same high latency.
No changes were made to the website around the time the latency increased.
There is no increase in the number of errors to the users.
You expect another spike in website traffic in the coming days and want to make sure users don't experience latency. What should you do?

• A.Upgrade the GCS buckets to Multi-Regional.
• B.Enable high availability on the CloudSQL instances.
• C.Move the application from App Engine to Compute Engine.
• D.Modify the App Engine configuration to have additional idle instances.

Comment: *

Name: *

Email: *

Verification: *

You are responsible for creating and modifying the Terraform templates that define your Infrastructure. Because two new engineers will also be working on the same code, you need to define a process and adopt a tool that will prevent you from overwriting each other's code. You also want to ensure that you capture all updates in the latest version. What should you do?

• A.Store your code as text files in Google Drive in a defined folder structure that organizes the files.
  * At the end of each day, confirm that all changes have been captured in the files within the folder structure and create a new .zip archive with a predefined naming convention.
  * Upload the .zip archive to a versioned Cloud Storage bucket and accept it as the latest version.
• B.Store your code in a Git-based version control system.
  * Establish a process that includes code reviews by peers and unit testing to ensure integrity and functionality before integration of code.
  * Establish a process where the fully integrated code in the repository becomes the latest master version.
• C.Store your code in a Git-based version control system.
  * Establish a process that allows developers to merge their own changes at the end of each day.
  * Package and upload code lo a versioned Cloud Storage bucket as the latest master version.
• D.Store your code as text files in Google Drive in a defined folder structure that organizes the files.
  * At the end of each day. confirm that all changes have been captured in the files within the folder structure.
  * Rename the folder structure with a predefined naming convention that increments the version.

Comment: *

Name: *

Email: *

Verification: *

Your application images are built using Cloud Build and pushed to Google Container Registry (GCR). You want to be able to specify a particular version of your application for deployment based on the release version tagged in source control. What should you do when you push the image?

• A.Use GCR digest versioning to match the image to the tag in source control.
• B.Use Cloud Build to include the release version tag in the application image.
• C.Reference the image digest in the source control tag.
• D.Supply the source control tag as a parameter within the image name.

Comment: *

Name: *

Email: *

Verification: *

You are creating and assigning action items in a postmodern for an outage. The outage is over, but you need to address the root causes. You want to ensure that your team handles the action items quickly and efficiently.
How should you assign owners and collaborators to action items?

• A.Assign one owner for each action item and any necessary collaborators.
• B.Assign multiple owners for each item to guarantee that the team addresses items quickly
• C.Assign collaborators but no individual owners to the items to keep the postmortem blameless.
• D.Assign the team lead as the owner for all action items because they are in charge of the SRE team.

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

Comment: *

Name: *

Email: *

Verification: *