You are managing an application that exposes an HTTP endpoint without using a load balancer. The latency of the HTTP responses is important for the user experience. You want to understand what HTTP latencies all of your users are experiencing. You use Stackdriver Monitoring. What should you do?
https://sre.google/workbook/implementing-slos/
https://cloud.google.com/architecture/adopting-slos/
Latency is commonly measured as a distribution. Given a distribution, you can measure various percentiles. For example, you might measure the number of requests that are slower than the historical 99th percentile.
You work for a global organization and run a service with an availability target of 99% with limited engineering resources. For the current calendar month you noticed that the service has 99 5% availability. You must ensure that your service meets the defined availability goals and can react to business changes including the upcoming launch of new features You also need to reduce technical debt while minimizing operational costs You want to follow Google-recommended practices What should you do?
You are creating Cloud Logging sinks to export log entries from Cloud Logging to BigQuery for future analysis Your organization has a Google Cloud folder named Dev that contains development projects and a folder named Prod that contains production projects Log entries for development projects must be exported to dev_dataset. and log entries for production projects must be exported to prod_datasetYou need to minimize the number of log sinks created and you want to ensure that the log sinks apply to future projects What should you do?
The best option for minimizing the number of log sinks created and ensuring that the log sinks apply to future projects is to create an aggregated log sink in the Dev and Prod folders. An aggregated log sink is a log sink that collects logs from multiple sources, such as projects, folders, or organizations. By creating an aggregated log sink in each folder, you can export log entries for development projects to dev_dataset and log entries for production projects to prod_dataset. You can also use filters to specify which logs you want to export. Additionally, by creating an aggregated log sink at the folder level, you can ensure that the log sink applies to future projects that are created under that folder.
You are developing the deployment and testing strategies for your CI/CD pipeline in Google Cloud You must be able to
* Reduce the complexity of release deployments and minimize the duration of deployment rollbacks
* Test real production traffic with a gradual increase in the number of affected users
You want to select a deployment and testing strategy that meets your requirements What should you do?
The best option for selecting a deployment and testing strategy that meets your requirements is to use blue/green deployment and canary testing. A blue/green deployment is a deployment strategy that involves creating two identical environments, one running the current version of the application (blue) and one running the new version of the application (green). The traffic is switched from blue to green after testing the new version, and if any issues are discovered, the traffic can be switched back to blue instantly. This way, you can reduce the complexity of release deployments and minimize the duration of deployment rollbacks. A canary testing is a testing strategy that involves releasing a new version of an application to a subset of users or servers and monitoring its performance and reliability. This way, you can test real production traffic with a gradual increase in the number of affected users.
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?
When disaster strikes, the person who declares the incident typically steps into the IC role and directs the high-level state of the incident. The IC concentrates on the 3Cs and does the following: Commands and coordinates the incident response, delegating roles as needed. By default, the IC assumes all roles that have not been delegated yet. Communicates effectively. Stays in control of the incident response. Works with other responders to resolve the incident.https://sre.google/workbook/incident-response/
Dorothy Campbell
2 days agoChristopher Hill
21 days agoAngela Turner
1 month agoDavid Mitchell
2 months agoCrystal Peterson
2 months agoDennis Jackson
2 months agoDaniel Howard
2 months agoHeather Jackson
2 months agoSteven Torres
2 months agoStephen Williams
2 months agoRikki
3 months agoMaryann
3 months agoBasilia
4 months agoLai
4 months agoDaniela
4 months agoCassandra
4 months agoLeila
5 months agoSherron
5 months agoMakeda
5 months agoWalton
5 months agoGoldie
6 months agoChau
6 months agoLilli
6 months agoAnabel
6 months agoJarvis
7 months agoLindsey
7 months agoCristal
7 months agoZita
7 months agoCyril
8 months agoAdelaide
8 months agoOna
8 months agoKimbery
8 months agoPhung
9 months agoMelvin
9 months agoChrista
9 months agoJennie
9 months agoDana
10 months agoCandida
10 months agoKathrine
10 months agoDannette
10 months agoMerilyn
10 months agoEileen
1 year agoMargarita
1 year agoMauricio
1 year agoFernanda
1 year agoYolando
1 year agoMakeda
1 year agoTiffiny
1 year agoMaile
1 year agoShaunna
1 year agoRebbecca
1 year agoRebecka
1 year agoMaile
1 year agoTeri
1 year agoFelix
1 year agoMelissia
1 year agoGertude
1 year agoJosue
2 years agoAnika
2 years agoMargurite
2 years agoSelma
2 years agoKristian
2 years agoJanna
2 years agoKirby
2 years agoPhyliss
2 years agoSkye
2 years agoPeggie
2 years agoSharan
2 years agoMollie
2 years agoNovella
2 years agoLynette
2 years agoFiliberto
2 years agoToi
2 years agoKeva
2 years agoBerry
2 years agoMaynard
2 years agoRosenda
2 years agoMicheline
2 years agoHelga
2 years agoJoana
2 years agoSunny
2 years agoAliza
2 years agoTracie
2 years agoJimmy
2 years ago