Your team is designing a new application for deployment into Google Kubernetes Engine (GKE). You need to set up monitoring to collect and aggregate various application-level metrics in a centralized location. You want to use Google Cloud Platform services while minimizing the amount of work required to set up monitoring.
What should you do?

• A.Publish various metrics from the application directly to the Slackdriver Monitoring API, and then observe these custom metrics in Stackdriver.
• B.Install the Cloud Pub/Sub client libraries, push various metrics from the application to various topics, and then observe the aggregated metrics in Stackdriver.
• C.Install the OpenTelemetry client libraries in the application, configure Stackdriver as the export destination for the metrics, and then observe the application's metrics in Stackdriver.
• D.Emit all metrics in the form of application-specific log messages, pass these messages from the containers to the Stackdriver logging collector, and then observe metrics in Stackdriver.

Comment: *

Name: *

Email: *

Verification: *

You support a user-facing web application. When analyzing the application's error budget over the previous six months, you notice that the application has never consumed more than 5% of its error budget in any given time window. You hold a Service Level Objective (SLO) review with business stakeholders and confirm that the SLO is set appropriately. You want your application's SLO to more closely reflect its observed reliability.
What steps can you take to further that goal while balancing velocity, reliability, and business needs? (Choose two.)

• A.Add more serving capacity to all of your application's zones.
• B.Have more frequent or potentially risky application releases.
• C.Tighten the SLO match the application's observed reliability.
• D.Implement and measure additional Service Level Indicators (SLIs) fro the application.
• E.Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.

Comment: *

Name: *

Email: *

Verification: *

You are writing a postmortem for an incident that severely affected users. You want to prevent similar incidents in the future. Which two of the following sections should you include in the postmortem? (Choose two.)

• A.An explanation of the root cause of the incident
• B.A list of employees responsible for causing the incident
• C.A list of action items to prevent a recurrence of the incident
• D.Your opinion of the incident's severity compared to past incidents
• E.Copies of the design documents for all the services impacted by the incident

Comment: *

Name: *

Email: *

Verification: *

Your company experiences bugs, outages, and slowness in its production systems. Developers use the production environment for new feature development and bug fixes. Configuration and experiments are done in the production environment, causing outages for users. Testers use the production environment for load testing, which often slows the production systems. You need to redesign the environment to reduce the number of bugs and outages in production and to enable testers to load test new features. What should you do?

• A.Secure the production environment to ensure that developers can't change it and set up one controlled update per year.
• B.Create a development environment for writing code and a test environment for configurations, experiments, and load testing.
• C.Create an automated testing script in production to detect failures as soon as they occur.
• D.Create a development environment with smaller server capacity and give access only to developers and testers.

Comment: *

Name: *

Email: *

Verification: *

Your organization recently adopted a container-based workflow for application development. Your team develops numerous applications that are deployed continuously through an automated build pipeline to a Kubernetes cluster in the production environment. The security auditor is concerned that developers or operators could circumvent automated testing and push code changes to production without approval. What should you do to enforce approvals?

• A.Leverage Kubernetes Role-Based Access Control (RBAC) to restrict access to only approved users.
• B.Use an Admission Controller to verify that incoming requests originate from approved sources.
• C.Configure the build system with protected branches that require pull request approval.
• D.Enable binary authorization inside the Kubernetes cluster and configure the build pipeline as an attestor.

Comment: *

Name: *

Email: *

Verification: *