- (Topic 5)
You need to set up Microsoft SQL Server on GCP. Management requires that there’s no downtime in case of a data center outage in any of the zones within a GCP region. What should you do?

1. A. Configure a Cloud SQL instance with high availability enabled.
2. B. Configure a Cloud Spanner instance with a regional instance configuration.
3. C. Set up SQL Server on Compute Engine, using Always On Availability Groups using Windows FailoverClusterin
4. D. Place nodes in different subnets.
5. E. Set up SQL Server Always On Availability Groups using Windows Failover Clusterin
6. F. Place nodes in different zones.

Correct Answer: D
https://cloud.google.com/sql/docs/sqlserver/configure-ha

- (Topic 5)
You have an outage in your Compute Engine managed instance group: all instance keep restarting after 5 seconds. You have a health check configured, but autoscaling is disabled. Your colleague, who is a Linux expert, offered to look into the issue. You need to make sure that he can access the VMs. What should you do?

1. A. Grant your colleague the IAM role of project Viewer
2. B. Perform a rolling restart on the instance group
3. C. Disable the health check for the instance grou
4. D. Add his SSH key to the project-wide SSH keys
5. E. Disable autoscaling for the instance grou
6. F. Add his SSH key to the project-wide SSH Keys

Correct Answer: C
https://cloud.google.com/compute/docs/instance-groups/autohealing-instances-in-migs Health checks used for autohealing should be conservative so they don't preemptively delete and recreate your instances. When an autohealer health check is too aggressive, the autohealer might mistake busy instances for failed instances and unnecessarily restart them, reducing availability

- (Topic 5)
You have deployed an application on Anthos clusters (formerly Anthos GKE). According to the SRE practices at your company you need to be alerted if the request latency is above a certain threshold for a specified amount of time. What should you do?

1. A. Enable the Cloud Trace API on your project and use Cloud Monitoring Alerts to send an alert based on the Cloud Trace metrics
2. B. Configure Anthos Config Management on your cluster and create a yaml file that defines the SLO and alerting policy you want to deploy in your cluster
3. C. Use Cloud Profiler to follow up the request latenc
4. D. Create a custom metric in Cloud Monitoring based on the results of Cloud Profiler, and create an Alerting Policy in case this metric exceeds the threshold
5. E. Install Anthos Service Mesh on your cluste
6. F. Use the Google Cloud Console to define a Service Level Objective (SLO)

Correct Answer: D
https://cloud.google.com/service-mesh/docs/overview https://cloud.google.com/service-mesh/docs/observability/slo-overview

- (Topic 5)
Your company has an application running as a Deployment in a Google Kubernetes Engine (GKE) cluster When releasing new versions of the application via a rolling deployment, the team has been causing outages The root cause of the outages is misconfigurations with parameters that are only used in production You want to put preventive measures for this in the platform to prevent outages What should you do?

1. A. Configure liveness and readiness probes in the Pod specification
2. B. Configure an uptime alert in Cloud Monitoring
3. C. Create a Scheduled Task to check whether the application is available
4. D. Configure health checks on the managed instance group

Correct Answer: D
This option can help prevent outages caused by misconfigurations with parameters that are only used in production. Liveness and readiness probes are mechanisms to check the health and availability of the Pods and containers in a GKE cluster. Liveness probes determine if a container is still running, and if not, restart it. Readiness probes determine if a container is ready to serve requests, and if not, remove it from the load balancer. By configuring liveness and readiness probes in the Pod specification, you can ensure that your application can handle traffic and recover from failures gracefully during a rolling update. The other options are not optimal for this scenario, because they either do not prevent outages, but only alert or monitor them (B, C), or do not apply to GKE clusters, but to Compute Engine instances (D). References:
✑ https://cloud.google.com/kubernetes-engine/docs/how-to/updating-apps
✑ https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best- practices-setting-up-health-checks-with-readiness-and-liveness-probes

- (Topic 5)
Your customer wants to capture multiple GBs of aggregate real-time key performance indicators (KPIs) from their game servers running on Google Cloud Platform and monitor the KPIs with low latency. How should they capture the KPIs?

1. A. Store time-series data from the game servers in Google Bigtable, and view it using Google Data Studio.
2. B. Output custom metrics to Stackdriver from the game servers, and create a Dashboard in StackdriverMonitoring Console to view them.
3. C. Schedule BigQuery load jobs to ingest analytics files uploaded to Cloud Storage every ten minutes, and visualize the results in Google Data Studio.
4. D. Insert the KPIs into Cloud Datastore entities, and run ad hoc analysis and visualizations of them in Cloud Datalab.

Correct Answer: A
https://cloud.google.com/monitoring/api/v3/metrics-details#metric-kinds