Enable the Cloud Trace API on your project and use Cloud Monitoring Alerts to send an alert based on the Cloud Trace metrics

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

Use Cloud Profiler to follow up the request latency. 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

Install Anthos Service Mesh on your cluster. Use the Google Cloud Console to define a Service Level Objective (SLO)

Configure a cron job to use the gcloud tool to take regular backups using persistent disk snapshots.

Mount a Local SSD volume as the backup location. After the backup is complete, use gsutil to move the
backup to Google Cloud Storage.

Use gcsfuse to mount a Google Cloud Storage bucket as a volume directly on the instance and write
backups to the mounted location using mysqldump

Mount additional persistent disk volumes onto each virtual machine (VM) instance in a RAID10 array
and use LVM to create snapshots to send to Cloud Storage.

Cloud Bigtable

Cloud Spanner

BigQuery

Cloud Datastore

Create a group per country. Add analysts to their respective country-groups. Create a
single group
‘all_analysts’, and add all country-groups as members. Grant the ‘all-analysis’ group the
IAM role of
BigQuery jobUser. Share the appropriate dataset with view access with each respective
analyst country-group

Create a group per country. Add analysts to their respective country-groups. Create a
single group
‘all_analysts’, and add all country-groups as members. Grant the ‘all-analysis’ group the
IAM role of
BigQuery jobUser. Share the appropriate tables with view access with each respective
analyst countrygroup.

Create a group per country. Add analysts to their respective country-groups. Create a
single group
‘all_analysts’, and add all country-groups as members. Grant the ‘all-analysis’ group the
IAM role of
BigQuery dataViewer. Share the appropriate dataset with view access with each respective
analyst
country-group.

Create a group per country. Add analysts to their respective country-groups. Create a
single group
‘all_analysts’, and add all country-groups as members. Grant the ‘all-analysis’ group the
IAM role of
BigQuery dataViewer. Share the appropriate table with view access with each respective
analyst countrygroup.

Grant the security team access to the logs in each Project.

Configure Stackdriver Monitoring for all Projects, and export to BigQuery.

Configure Stackdriver Monitoring for all Projects with the default retention policies.

Configure Stackdriver Monitoring for all Projects, and export to Google Cloud Storage.

1. Update your GKE cluster to use Cloud Operations for GKE.
2. Use the GKE Monitoring dashboard to investigate logs from affected Pods.

1. Create a new GKE cluster with Cloud Operations for GKE enabled.
2.Migrate the affected Pods to the new cluster, and redirect traffic for those Pods to the new cluster.
3.Use the GKE Monitoring dashboard to investigate logs from affected Pods.

1. Update your GKE cluster to use Cloud Operations for GKE, and deploy Prometheus. 2. Set an alert to trigger whenever the application returns an error.

1. Create a new GKE cluster with Cloud Operations for GKE enabled, and deploy
Prometheus.
2.Migrate the affected Pods to the new cluster, and redirect traffic for those Pods to the
new cluster.
3.Set an alert to trigger whenever the application returns an error

Use the Admin Directory API to authenticate against the Active Directory domain controller.

Use Google Cloud Directory Sync to synchronize Active Directory usernames with cloud identities and
configure SAML SSO.

Use Cloud Identity-Aware Proxy configured to use the on-premises Active Directory domain controller
as an identity provider.

Use Compute Engine to create an Active Directory (AD) domain controller that is a replica of the
onpremises AD domain controller using Google Cloud Directory Sync.