About Google Professional Cloud DevOps Engineer<\/strong><\/h3>\n\n\n\nThe Google Professional Cloud Devops Engineer Certification exam is intended to assess technical skills relevant to the job role. Candidates who are preparing for the exam should have practical experience. The Google Professional Cloud DevOps Engineer exam evaluates candidates’ abilities to \u2013<\/p>\n\n\n\n
\n- To begin, apply principles of site reliability engineering to a service.<\/li>\n\n\n\n
- Second, improve service performance.<\/li>\n\n\n\n
- Following that, put in place service monitoring strategies.<\/li>\n\n\n\n
- Additionally, create and implement CI\/CD pipelines for a service.<\/li>\n\n\n\n
- Finally, handle service incidents.<\/li>\n<\/ul>\n\n\n\n
Who should take the exam?<\/strong><\/h4>\n\n\n\nCandidates who plan to take the Google Cloud Platform Professional Cloud Devops Engineer exam will be in charge of efficient development operations that balance service reliability and delivery speed. They should also be able to build software delivery pipelines, deploy and monitor services, and manage and learn from incidents using the Google Cloud Platform.<\/p>\n\n\n\n
Let us now move towards the main aim of this article – <\/em><\/p>\n\n\n\nHow to become a Google Professional Cloud DevOps Engineer?<\/strong><\/h3>\n\n\n\nWhen it comes to the Google Professional Cloud DevOps Engineer Exam, it is critical that you make the right decision and embark on a successful and rewarding career in the Google cloud platform. So let’s get started with the planning.<\/p>\n\n\n
\n![\"\"](\"https:\/\/www.testpreptraining.ai\/blog\/wp-content\/uploads\/2022\/01\/How-to-become-a-Google-Professional-Cloud-DevOps-Engineer-3.png\")
<\/figure>\n<\/div>\n\n\nStep 1 \u2013 Know in-depth about the exam syllabus<\/strong><\/h5>\n\n\n\nBelow mentioned is the detailed course outline for the exam along with the documentation and whitepapers offered by google \u2013<\/p>\n\n\n\n
Topic 1: Bootstrapping a Google Cloud organization for DevOps (17%)<\/strong><\/h5>\n\n\n\n 1.1 Designing the overall resource hierarchy for an organization. Considerations include:<\/p>\n\n\n\n
\n- Projects and folders (Google Documentation:<\/strong> Creating and managing Folders<\/a>)<\/li>\n\n\n\n
- Shared networking (Google Documentation:<\/strong> Shared VPC<\/a>)<\/li>\n\n\n\n
- Identity and Access Management (IAM) roles and organization-level policies (Google Documentation:<\/strong> IAM overview<\/a>)<\/li>\n\n\n\n
- Creating and managing service accounts (Google Documentation:<\/strong> Create a service account<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.2 Managing infrastructure as code. Considerations include:<\/p>\n\n\n\n
\n- Infrastructure as code tooling (e.g., Cloud Foundation Toolkit, Config Connector, Terraform, Helm) (Google Documentation:<\/strong> Config Connector overview<\/a>, Infrastructure as Code on Google Cloud<\/a>)<\/li>\n\n\n\n
- Making infrastructure changes using Google-recommended practices and infrastructure as code blueprints (Google Documentation:<\/strong> Using Recommendations for Infrastructure as Code<\/a>)<\/li>\n\n\n\n
- Immutable architecture (Google Documentation:<\/strong> Best practices for operating containers<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.3 Designing a CI\/CD architecture stack in Google Cloud, hybrid, and multi-cloud environments. Considerations include:<\/p>\n\n\n\n
\n- CI with Cloud Build (Google Documentation:<\/strong> Cloud Build<\/a>, Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- CD with Google Cloud Deploy (Google Documentation:<\/strong> Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- Widely used third-party tooling (e.g., Jenkins, Git, ArgoCD, Packer)<\/li>\n\n\n\n
- Security of CI\/CD tooling (Google Documentation:<\/strong> Building a secure CI\/CD pipeline using Google Cloud built-in services<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.4 Managing multiple environments (e.g., staging, production). Considerations include:<\/p>\n\n\n\n
\n- Determining the number of environments and their purpose (Google Documentation:<\/strong> Create Cloud Composer environments<\/a>)<\/li>\n\n\n\n
- Creating environments dynamically for each feature branch with Google Kubernetes Engine (GKE) and Terraform (Google Documentation:<\/strong> Create a GKE cluster and deploy a workload using Terraform<\/a>, Modern CI\/CD with GKE: Build a CI\/CD system<\/a>)<\/li>\n\n\n\n
- Config Management (Google Documentation:<\/strong> Configurations Overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 2: Building and implementing CI\/CD pipelines for a service (23%)<\/strong><\/h5>\n\n\n\n2.1 Designing and managing CI\/CD pipelines. Considerations include:<\/p>\n\n\n\n
\n- Artifact management with Artifact Registry (Google Documentation:<\/strong> Artifact Registry overview<\/a>)<\/li>\n\n\n\n
- Deployment to hybrid and multi-cloud environments (e.g., Anthos, GKE) (Google Documentation:<\/strong> GKE Multi-Cloud documentation<\/a>, Anthos<\/a>)<\/li>\n\n\n\n
- CI\/CD pipeline triggers (Google Documentation:<\/strong> Cloud Build triggers<\/a>)<\/li>\n\n\n\n
- Testing a new application version in the pipeline (Google Documentation:<\/strong> Test and deploy your application<\/a>)<\/li>\n\n\n\n
- Configuring deployment processes (e.g., approval flows) (Google Documentation:<\/strong> Setting up a CI\/CD pipeline for your data-processing workflow<\/a>)<\/li>\n\n\n\n
- CI\/CD of serverless applications (Google Documentation:<\/strong> Cloud Build<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.2 Implement CI\/CD pipelines:<\/p>\n\n\n\n
\n- Auditing and tracking deployments (e.g., Artifact Registry, Cloud Build, Google Cloud Deploy, Cloud Audit Logs) (Google Documentation:<\/strong> Artifact Registry audit logging<\/a>, Cloud Audit Logs overview<\/a>)<\/li>\n\n\n\n
- Deployment strategies (e.g., canary, blue\/green, rolling, traffic splitting)<\/li>\n\n\n\n
- Rollback strategies (Google Documentation:<\/strong> Rollbacks, gradual rollouts, and traffic migration<\/a>)<\/li>\n\n\n\n
- Troubleshooting deployment issues (Google Documentation:<\/strong> Troubleshooting deployments<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.3 Managing CI\/CD configuration and secrets. Considerations include:<\/p>\n\n\n\n
\n- Secure storage methods and key rotation services (e.g., Cloud Key Management Service, Secret Manager) (Google Documentation:<\/strong> Secret Manager<\/a><\/strong>)<\/li>\n\n\n\n
- Secret management (Google Documentation:<\/strong> Secret Manager<\/a>)<\/li>\n\n\n\n
- Build versus runtime secret injection (Google Documentation:<\/strong> Configure secrets<\/a>, Use secrets from Secret Manager<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.4 Securing the CI\/CD deployment pipeline. Considerations include:<\/p>\n\n\n\n
\n- Vulnerability analysis with Artifact Registry Artifact analysis and vulnerability scanning<\/a>)<\/li>\n\n\n\n
- Binary Authorization (Google Documentation:<\/strong> Binary Authorization<\/a>)<\/li>\n\n\n\n
- IAM policies per environment<\/li>\n<\/ul>\n\n\n\n
Section 3: Applying site reliability engineering practices to a service (23%)<\/strong><\/h5>\n\n\n\n 3.1 Balancing change, velocity, and reliability of the service. Considerations include:<\/p>\n\n\n\n
\n- Discovering SLIs (e.g., availability, latency) (Google Documentation:<\/strong> Choose your service level indicators (SLIs)<\/a>)<\/li>\n\n\n\n
- Defining SLOs and understanding SLAs (Google Documentation:<\/strong> SRE fundamentals: SLIs, SLAs and SLOs<\/a>)<\/li>\n\n\n\n
- Error budgets (Google Documentation:<\/strong> Concepts in service monitoring<\/a>)<\/li>\n\n\n\n
- Toil automation<\/li>\n\n\n\n
- Opportunity cost of risk and reliability (e.g., number of \u201cnines\u201d)<\/li>\n<\/ul>\n\n\n\n
3.2 Managing service lifecycle. Considerations include:<\/p>\n\n\n\n
\n- Service management (e.g., introduction of a new service by using a pre-service onboarding checklist, launch plan, or deployment plan, deployment, maintenance, and retirement) (Google Documentation:<\/strong> Google Cloud setup checklist<\/a>)<\/li>\n\n\n\n
- Capacity planning (e.g., quotas and limits management) (Google Documentation:<\/strong> Quotas & limits<\/a>)<\/li>\n\n\n\n
- Autoscaling using managed instance groups, Cloud Run, Cloud Functions, or GKE (Google Documentation:<\/strong> Autoscaling groups of instances<\/a>)<\/li>\n\n\n\n
- Implementing feedback loops to improve a service (Google Documentation:<\/strong> Feedback prebuilt component<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.3 Ensuring healthy communication and collaboration for operations. Considerations include:<\/p>\n\n\n\n
\n- Preventing burnout (e.g., setting up automation processes to prevent burnout)<\/li>\n\n\n\n
- Fostering a culture of learning and blamelessness (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n\n\n\n
- Establishing joint ownership of services to eliminate team silos (Google Documentation:<\/strong> Guide to Cloud Billing Resource Organization & Access Management<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.4 Mitigating incident impact on users. Considerations include:<\/p>\n\n\n\n
\n- Communicating during an incident (Google Documentation:<\/strong> Data incident response process<\/a>)<\/li>\n\n\n\n
- Draining\/redirecting traffic (Google Documentation:<\/strong> Enable connection draining<\/a>)<\/li>\n\n\n\n
- Adding capacity (Google Documentation:<\/strong> Scale capacity<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.5 Conducting a postmortem. Considerations include:<\/p>\n\n\n\n
\n- Documenting root causes (Google Documentation:<\/strong> Error Reporting<\/a>)<\/li>\n\n\n\n
- Creating and prioritizing action items<\/li>\n\n\n\n
- Communicating the postmortem to stakeholders (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 4: Implementing service monitoring strategies (21%)<\/strong><\/h5>\n\n\n\n4.1 Managing logs:<\/p>\n\n\n\n
\n- Collecting structured and unstructured logs from Compute Engine, GKE, and serverless platforms using Cloud Logging (Google Documentation:<\/strong> About GKE logs<\/a>, Structured Logging<\/a>)<\/li>\n\n\n\n
- Configuring the Cloud Logging agent (Google Documentation:<\/strong> Configure the Logging agent<\/a>)<\/li>\n\n\n\n
- Collecting logs from outside Google Cloud (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Sending application logs directly to the Cloud Logging API (Google Documentation:<\/strong> Cloud Logging API<\/a>)<\/li>\n\n\n\n
- Log levels (e.g., info, error, debug, fatal) (Google Documentation:<\/strong> View and write Cloud Function logs<\/a>)<\/li>\n\n\n\n
- Optimizing logs (e.g., multiline logging, exceptions, size, cost) (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.2 Managing metrics with Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
\n- Collecting and analyzing application and platform metrics (Google Documentation:<\/strong> Collect metrics overview<\/a>)<\/li>\n\n\n\n
- Collecting networking and service mesh metrics (Google Documentation:<\/strong> Observability overview<\/a>, Cloud Service Mesh overview<\/a>)<\/li>\n\n\n\n
- Use metric explorer for ad hoc metric analysis (Google Documentation:<\/strong> Metrics Explorer<\/a>)<\/li>\n\n\n\n
- Creating custom metrics from logs (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.3 Managing dashboards and alerts in Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
\n- Creating a monitoring dashboard (Google Documentation:<\/strong> Create and manage custom dashboards<\/a>)<\/li>\n\n\n\n
- Filtering and sharing dashboards (Google Documentation:<\/strong> Share a custom dashboard<\/a>)<\/li>\n\n\n\n
- Configuring alerting<\/li>\n\n\n\n
- Defining alerting policies based on SLOs and SLIs (Google Documentation:<\/strong> Creating an alerting policy<\/a>)<\/li>\n\n\n\n
- Automating alerting policy definition using Terraform (Google Documentation:<\/strong> Create alerting policies with Terraform<\/a>, Manage alerting policies with Terraform<\/a>)<\/li>\n\n\n\n
- Using Google Cloud Managed Service for Prometheus to collect metrics and set up monitoring and alerting (Google Documentation:<\/strong> Google Cloud Managed Service for Prometheus<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.4 Managing Cloud Logging platform. Considerations include:<\/p>\n\n\n\n
\n- Enabling data access logs (e.g., Cloud Audit Logs) (Google Documentation:<\/strong> Enable Data Access audit logs<\/a>)<\/li>\n\n\n\n
- Enabling VPC Flow Logs (Google Documentation:<\/strong> Use VPC Flow Logs<\/a>)<\/li>\n\n\n\n
- Viewing logs in the Google Cloud console<\/li>\n\n\n\n
- Using basic versus advanced log filters (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n\n\n\n
- Logs exclusion versus logs export<\/li>\n\n\n\n
- Project-level versus organization-level export<\/li>\n\n\n\n
- Managing and viewing log exports (Google Documentation:<\/strong> Viewing activity logs<\/a>)<\/li>\n\n\n\n
- Sending logs to an external logging platform (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Filtering and redacting sensitive data (e.g., personally identifiable information [PII], protected health information [PHI]) (Google Documentation:<\/strong> De-identifying sensitive data<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.5 Implementing logging and monitoring access controls. Considerations include:<\/p>\n\n\n\n
\n- Restricting access to audit logs and VPC Flow Logs with Cloud Logging (Google Documentation:<\/strong> VPC audit logging information<\/a>)<\/li>\n\n\n\n
- Restricting export configuration with Cloud Logging (Google Documentation:<\/strong> Scenarios for exporting Cloud Logging: Compliance requirements<\/a>)<\/li>\n\n\n\n
- Allowing metric and log writing with Cloud Monitoring (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 5: Optimizing service performance (16%)<\/strong><\/h5>\n\n\n\n5.1 Identify service performance issues:<\/p>\n\n\n\n
\n- Using Google Cloud\u2019s operations suite to identify cloud resource utilization (Google Documentation:<\/strong> Observability in Google Cloud<\/a>)<\/li>\n\n\n\n
- Interpret service mesh telemetry (Google Documentation:<\/strong> The service mesh era<\/a>)<\/li>\n\n\n\n
- Troubleshooting issues with compute resources (Google Documentation:<\/strong> Troubleshooting resource availability errors<\/a>)<\/li>\n\n\n\n
- Troubleshooting deploy time and runtime issues with applications (Google Documentation:<\/strong>
Who should take the exam?<\/strong><\/h4>\n\n\n\nCandidates who plan to take the Google Cloud Platform Professional Cloud Devops Engineer exam will be in charge of efficient development operations that balance service reliability and delivery speed. They should also be able to build software delivery pipelines, deploy and monitor services, and manage and learn from incidents using the Google Cloud Platform.<\/p>\n\n\n\n
Let us now move towards the main aim of this article – <\/em><\/p>\n\n\n\nHow to become a Google Professional Cloud DevOps Engineer?<\/strong><\/h3>\n\n\n\nWhen it comes to the Google Professional Cloud DevOps Engineer Exam, it is critical that you make the right decision and embark on a successful and rewarding career in the Google cloud platform. So let’s get started with the planning.<\/p>\n\n\n
\n<\/figure>\n<\/div>\n\n\nStep 1 \u2013 Know in-depth about the exam syllabus<\/strong><\/h5>\n\n\n\nBelow mentioned is the detailed course outline for the exam along with the documentation and whitepapers offered by google \u2013<\/p>\n\n\n\n
Topic 1: Bootstrapping a Google Cloud organization for DevOps (17%)<\/strong><\/h5>\n\n\n\n 1.1 Designing the overall resource hierarchy for an organization. Considerations include:<\/p>\n\n\n\n
\n- Projects and folders (Google Documentation:<\/strong> Creating and managing Folders<\/a>)<\/li>\n\n\n\n
- Shared networking (Google Documentation:<\/strong> Shared VPC<\/a>)<\/li>\n\n\n\n
- Identity and Access Management (IAM) roles and organization-level policies (Google Documentation:<\/strong> IAM overview<\/a>)<\/li>\n\n\n\n
- Creating and managing service accounts (Google Documentation:<\/strong> Create a service account<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.2 Managing infrastructure as code. Considerations include:<\/p>\n\n\n\n
\n- Infrastructure as code tooling (e.g., Cloud Foundation Toolkit, Config Connector, Terraform, Helm) (Google Documentation:<\/strong> Config Connector overview<\/a>, Infrastructure as Code on Google Cloud<\/a>)<\/li>\n\n\n\n
- Making infrastructure changes using Google-recommended practices and infrastructure as code blueprints (Google Documentation:<\/strong> Using Recommendations for Infrastructure as Code<\/a>)<\/li>\n\n\n\n
- Immutable architecture (Google Documentation:<\/strong> Best practices for operating containers<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.3 Designing a CI\/CD architecture stack in Google Cloud, hybrid, and multi-cloud environments. Considerations include:<\/p>\n\n\n\n
\n- CI with Cloud Build (Google Documentation:<\/strong> Cloud Build<\/a>, Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- CD with Google Cloud Deploy (Google Documentation:<\/strong> Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- Widely used third-party tooling (e.g., Jenkins, Git, ArgoCD, Packer)<\/li>\n\n\n\n
- Security of CI\/CD tooling (Google Documentation:<\/strong> Building a secure CI\/CD pipeline using Google Cloud built-in services<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.4 Managing multiple environments (e.g., staging, production). Considerations include:<\/p>\n\n\n\n
\n- Determining the number of environments and their purpose (Google Documentation:<\/strong> Create Cloud Composer environments<\/a>)<\/li>\n\n\n\n
- Creating environments dynamically for each feature branch with Google Kubernetes Engine (GKE) and Terraform (Google Documentation:<\/strong> Create a GKE cluster and deploy a workload using Terraform<\/a>, Modern CI\/CD with GKE: Build a CI\/CD system<\/a>)<\/li>\n\n\n\n
- Config Management (Google Documentation:<\/strong> Configurations Overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 2: Building and implementing CI\/CD pipelines for a service (23%)<\/strong><\/h5>\n\n\n\n2.1 Designing and managing CI\/CD pipelines. Considerations include:<\/p>\n\n\n\n
\n- Artifact management with Artifact Registry (Google Documentation:<\/strong> Artifact Registry overview<\/a>)<\/li>\n\n\n\n
- Deployment to hybrid and multi-cloud environments (e.g., Anthos, GKE) (Google Documentation:<\/strong> GKE Multi-Cloud documentation<\/a>, Anthos<\/a>)<\/li>\n\n\n\n
- CI\/CD pipeline triggers (Google Documentation:<\/strong> Cloud Build triggers<\/a>)<\/li>\n\n\n\n
- Testing a new application version in the pipeline (Google Documentation:<\/strong> Test and deploy your application<\/a>)<\/li>\n\n\n\n
- Configuring deployment processes (e.g., approval flows) (Google Documentation:<\/strong> Setting up a CI\/CD pipeline for your data-processing workflow<\/a>)<\/li>\n\n\n\n
- CI\/CD of serverless applications (Google Documentation:<\/strong> Cloud Build<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.2 Implement CI\/CD pipelines:<\/p>\n\n\n\n
\n- Auditing and tracking deployments (e.g., Artifact Registry, Cloud Build, Google Cloud Deploy, Cloud Audit Logs) (Google Documentation:<\/strong> Artifact Registry audit logging<\/a>, Cloud Audit Logs overview<\/a>)<\/li>\n\n\n\n
- Deployment strategies (e.g., canary, blue\/green, rolling, traffic splitting)<\/li>\n\n\n\n
- Rollback strategies (Google Documentation:<\/strong> Rollbacks, gradual rollouts, and traffic migration<\/a>)<\/li>\n\n\n\n
- Troubleshooting deployment issues (Google Documentation:<\/strong> Troubleshooting deployments<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.3 Managing CI\/CD configuration and secrets. Considerations include:<\/p>\n\n\n\n
\n- Secure storage methods and key rotation services (e.g., Cloud Key Management Service, Secret Manager) (Google Documentation:<\/strong> Secret Manager<\/a><\/strong>)<\/li>\n\n\n\n
- Secret management (Google Documentation:<\/strong> Secret Manager<\/a>)<\/li>\n\n\n\n
- Build versus runtime secret injection (Google Documentation:<\/strong> Configure secrets<\/a>, Use secrets from Secret Manager<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.4 Securing the CI\/CD deployment pipeline. Considerations include:<\/p>\n\n\n\n
\n- Vulnerability analysis with Artifact Registry Artifact analysis and vulnerability scanning<\/a>)<\/li>\n\n\n\n
- Binary Authorization (Google Documentation:<\/strong> Binary Authorization<\/a>)<\/li>\n\n\n\n
- IAM policies per environment<\/li>\n<\/ul>\n\n\n\n
Section 3: Applying site reliability engineering practices to a service (23%)<\/strong><\/h5>\n\n\n\n 3.1 Balancing change, velocity, and reliability of the service. Considerations include:<\/p>\n\n\n\n
\n- Discovering SLIs (e.g., availability, latency) (Google Documentation:<\/strong> Choose your service level indicators (SLIs)<\/a>)<\/li>\n\n\n\n
- Defining SLOs and understanding SLAs (Google Documentation:<\/strong> SRE fundamentals: SLIs, SLAs and SLOs<\/a>)<\/li>\n\n\n\n
- Error budgets (Google Documentation:<\/strong> Concepts in service monitoring<\/a>)<\/li>\n\n\n\n
- Toil automation<\/li>\n\n\n\n
- Opportunity cost of risk and reliability (e.g., number of \u201cnines\u201d)<\/li>\n<\/ul>\n\n\n\n
3.2 Managing service lifecycle. Considerations include:<\/p>\n\n\n\n
\n- Service management (e.g., introduction of a new service by using a pre-service onboarding checklist, launch plan, or deployment plan, deployment, maintenance, and retirement) (Google Documentation:<\/strong> Google Cloud setup checklist<\/a>)<\/li>\n\n\n\n
- Capacity planning (e.g., quotas and limits management) (Google Documentation:<\/strong> Quotas & limits<\/a>)<\/li>\n\n\n\n
- Autoscaling using managed instance groups, Cloud Run, Cloud Functions, or GKE (Google Documentation:<\/strong> Autoscaling groups of instances<\/a>)<\/li>\n\n\n\n
- Implementing feedback loops to improve a service (Google Documentation:<\/strong> Feedback prebuilt component<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.3 Ensuring healthy communication and collaboration for operations. Considerations include:<\/p>\n\n\n\n
\n- Preventing burnout (e.g., setting up automation processes to prevent burnout)<\/li>\n\n\n\n
- Fostering a culture of learning and blamelessness (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n\n\n\n
- Establishing joint ownership of services to eliminate team silos (Google Documentation:<\/strong> Guide to Cloud Billing Resource Organization & Access Management<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.4 Mitigating incident impact on users. Considerations include:<\/p>\n\n\n\n
\n- Communicating during an incident (Google Documentation:<\/strong> Data incident response process<\/a>)<\/li>\n\n\n\n
- Draining\/redirecting traffic (Google Documentation:<\/strong> Enable connection draining<\/a>)<\/li>\n\n\n\n
- Adding capacity (Google Documentation:<\/strong> Scale capacity<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.5 Conducting a postmortem. Considerations include:<\/p>\n\n\n\n
\n- Documenting root causes (Google Documentation:<\/strong> Error Reporting<\/a>)<\/li>\n\n\n\n
- Creating and prioritizing action items<\/li>\n\n\n\n
- Communicating the postmortem to stakeholders (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 4: Implementing service monitoring strategies (21%)<\/strong><\/h5>\n\n\n\n4.1 Managing logs:<\/p>\n\n\n\n
\n- Collecting structured and unstructured logs from Compute Engine, GKE, and serverless platforms using Cloud Logging (Google Documentation:<\/strong> About GKE logs<\/a>, Structured Logging<\/a>)<\/li>\n\n\n\n
- Configuring the Cloud Logging agent (Google Documentation:<\/strong> Configure the Logging agent<\/a>)<\/li>\n\n\n\n
- Collecting logs from outside Google Cloud (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Sending application logs directly to the Cloud Logging API (Google Documentation:<\/strong> Cloud Logging API<\/a>)<\/li>\n\n\n\n
- Log levels (e.g., info, error, debug, fatal) (Google Documentation:<\/strong> View and write Cloud Function logs<\/a>)<\/li>\n\n\n\n
- Optimizing logs (e.g., multiline logging, exceptions, size, cost) (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.2 Managing metrics with Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
\n- Collecting and analyzing application and platform metrics (Google Documentation:<\/strong> Collect metrics overview<\/a>)<\/li>\n\n\n\n
- Collecting networking and service mesh metrics (Google Documentation:<\/strong> Observability overview<\/a>, Cloud Service Mesh overview<\/a>)<\/li>\n\n\n\n
- Use metric explorer for ad hoc metric analysis (Google Documentation:<\/strong> Metrics Explorer<\/a>)<\/li>\n\n\n\n
- Creating custom metrics from logs (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.3 Managing dashboards and alerts in Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
\n- Creating a monitoring dashboard (Google Documentation:<\/strong> Create and manage custom dashboards<\/a>)<\/li>\n\n\n\n
- Filtering and sharing dashboards (Google Documentation:<\/strong> Share a custom dashboard<\/a>)<\/li>\n\n\n\n
- Configuring alerting<\/li>\n\n\n\n
- Defining alerting policies based on SLOs and SLIs (Google Documentation:<\/strong> Creating an alerting policy<\/a>)<\/li>\n\n\n\n
- Automating alerting policy definition using Terraform (Google Documentation:<\/strong> Create alerting policies with Terraform<\/a>, Manage alerting policies with Terraform<\/a>)<\/li>\n\n\n\n
- Using Google Cloud Managed Service for Prometheus to collect metrics and set up monitoring and alerting (Google Documentation:<\/strong> Google Cloud Managed Service for Prometheus<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.4 Managing Cloud Logging platform. Considerations include:<\/p>\n\n\n\n
\n- Enabling data access logs (e.g., Cloud Audit Logs) (Google Documentation:<\/strong> Enable Data Access audit logs<\/a>)<\/li>\n\n\n\n
- Enabling VPC Flow Logs (Google Documentation:<\/strong> Use VPC Flow Logs<\/a>)<\/li>\n\n\n\n
- Viewing logs in the Google Cloud console<\/li>\n\n\n\n
- Using basic versus advanced log filters (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n\n\n\n
- Logs exclusion versus logs export<\/li>\n\n\n\n
- Project-level versus organization-level export<\/li>\n\n\n\n
- Managing and viewing log exports (Google Documentation:<\/strong> Viewing activity logs<\/a>)<\/li>\n\n\n\n
- Sending logs to an external logging platform (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Filtering and redacting sensitive data (e.g., personally identifiable information [PII], protected health information [PHI]) (Google Documentation:<\/strong> De-identifying sensitive data<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.5 Implementing logging and monitoring access controls. Considerations include:<\/p>\n\n\n\n
\n- Restricting access to audit logs and VPC Flow Logs with Cloud Logging (Google Documentation:<\/strong> VPC audit logging information<\/a>)<\/li>\n\n\n\n
- Restricting export configuration with Cloud Logging (Google Documentation:<\/strong> Scenarios for exporting Cloud Logging: Compliance requirements<\/a>)<\/li>\n\n\n\n
- Allowing metric and log writing with Cloud Monitoring (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 5: Optimizing service performance (16%)<\/strong><\/h5>\n\n\n\n5.1 Identify service performance issues:<\/p>\n\n\n\n
\n- Using Google Cloud\u2019s operations suite to identify cloud resource utilization (Google Documentation:<\/strong> Observability in Google Cloud<\/a>)<\/li>\n\n\n\n
- Interpret service mesh telemetry (Google Documentation:<\/strong> The service mesh era<\/a>)<\/li>\n\n\n\n
- Troubleshooting issues with compute resources (Google Documentation:<\/strong> Troubleshooting resource availability errors<\/a>)<\/li>\n\n\n\n
- Troubleshooting deploy time and runtime issues with applications (Google Documentation:<\/strong>
How to become a Google Professional Cloud DevOps Engineer?<\/strong><\/h3>\n\n\n\nWhen it comes to the Google Professional Cloud DevOps Engineer Exam, it is critical that you make the right decision and embark on a successful and rewarding career in the Google cloud platform. So let’s get started with the planning.<\/p>\n\n\n
\n<\/figure>\n<\/div>\n\n\nStep 1 \u2013 Know in-depth about the exam syllabus<\/strong><\/h5>\n\n\n\nBelow mentioned is the detailed course outline for the exam along with the documentation and whitepapers offered by google \u2013<\/p>\n\n\n\n
Topic 1: Bootstrapping a Google Cloud organization for DevOps (17%)<\/strong><\/h5>\n\n\n\n 1.1 Designing the overall resource hierarchy for an organization. Considerations include:<\/p>\n\n\n\n
\n- Projects and folders (Google Documentation:<\/strong> Creating and managing Folders<\/a>)<\/li>\n\n\n\n
- Shared networking (Google Documentation:<\/strong> Shared VPC<\/a>)<\/li>\n\n\n\n
- Identity and Access Management (IAM) roles and organization-level policies (Google Documentation:<\/strong> IAM overview<\/a>)<\/li>\n\n\n\n
- Creating and managing service accounts (Google Documentation:<\/strong> Create a service account<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.2 Managing infrastructure as code. Considerations include:<\/p>\n\n\n\n
\n- Infrastructure as code tooling (e.g., Cloud Foundation Toolkit, Config Connector, Terraform, Helm) (Google Documentation:<\/strong> Config Connector overview<\/a>, Infrastructure as Code on Google Cloud<\/a>)<\/li>\n\n\n\n
- Making infrastructure changes using Google-recommended practices and infrastructure as code blueprints (Google Documentation:<\/strong> Using Recommendations for Infrastructure as Code<\/a>)<\/li>\n\n\n\n
- Immutable architecture (Google Documentation:<\/strong> Best practices for operating containers<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.3 Designing a CI\/CD architecture stack in Google Cloud, hybrid, and multi-cloud environments. Considerations include:<\/p>\n\n\n\n
\n- CI with Cloud Build (Google Documentation:<\/strong> Cloud Build<\/a>, Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- CD with Google Cloud Deploy (Google Documentation:<\/strong> Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- Widely used third-party tooling (e.g., Jenkins, Git, ArgoCD, Packer)<\/li>\n\n\n\n
- Security of CI\/CD tooling (Google Documentation:<\/strong> Building a secure CI\/CD pipeline using Google Cloud built-in services<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.4 Managing multiple environments (e.g., staging, production). Considerations include:<\/p>\n\n\n\n
\n- Determining the number of environments and their purpose (Google Documentation:<\/strong> Create Cloud Composer environments<\/a>)<\/li>\n\n\n\n
- Creating environments dynamically for each feature branch with Google Kubernetes Engine (GKE) and Terraform (Google Documentation:<\/strong> Create a GKE cluster and deploy a workload using Terraform<\/a>, Modern CI\/CD with GKE: Build a CI\/CD system<\/a>)<\/li>\n\n\n\n
- Config Management (Google Documentation:<\/strong> Configurations Overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 2: Building and implementing CI\/CD pipelines for a service (23%)<\/strong><\/h5>\n\n\n\n2.1 Designing and managing CI\/CD pipelines. Considerations include:<\/p>\n\n\n\n
\n- Artifact management with Artifact Registry (Google Documentation:<\/strong> Artifact Registry overview<\/a>)<\/li>\n\n\n\n
- Deployment to hybrid and multi-cloud environments (e.g., Anthos, GKE) (Google Documentation:<\/strong> GKE Multi-Cloud documentation<\/a>, Anthos<\/a>)<\/li>\n\n\n\n
- CI\/CD pipeline triggers (Google Documentation:<\/strong> Cloud Build triggers<\/a>)<\/li>\n\n\n\n
- Testing a new application version in the pipeline (Google Documentation:<\/strong> Test and deploy your application<\/a>)<\/li>\n\n\n\n
- Configuring deployment processes (e.g., approval flows) (Google Documentation:<\/strong> Setting up a CI\/CD pipeline for your data-processing workflow<\/a>)<\/li>\n\n\n\n
- CI\/CD of serverless applications (Google Documentation:<\/strong> Cloud Build<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.2 Implement CI\/CD pipelines:<\/p>\n\n\n\n
\n- Auditing and tracking deployments (e.g., Artifact Registry, Cloud Build, Google Cloud Deploy, Cloud Audit Logs) (Google Documentation:<\/strong> Artifact Registry audit logging<\/a>, Cloud Audit Logs overview<\/a>)<\/li>\n\n\n\n
- Deployment strategies (e.g., canary, blue\/green, rolling, traffic splitting)<\/li>\n\n\n\n
- Rollback strategies (Google Documentation:<\/strong> Rollbacks, gradual rollouts, and traffic migration<\/a>)<\/li>\n\n\n\n
- Troubleshooting deployment issues (Google Documentation:<\/strong> Troubleshooting deployments<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.3 Managing CI\/CD configuration and secrets. Considerations include:<\/p>\n\n\n\n
\n- Secure storage methods and key rotation services (e.g., Cloud Key Management Service, Secret Manager) (Google Documentation:<\/strong> Secret Manager<\/a><\/strong>)<\/li>\n\n\n\n
- Secret management (Google Documentation:<\/strong> Secret Manager<\/a>)<\/li>\n\n\n\n
- Build versus runtime secret injection (Google Documentation:<\/strong> Configure secrets<\/a>, Use secrets from Secret Manager<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.4 Securing the CI\/CD deployment pipeline. Considerations include:<\/p>\n\n\n\n
\n- Vulnerability analysis with Artifact Registry Artifact analysis and vulnerability scanning<\/a>)<\/li>\n\n\n\n
- Binary Authorization (Google Documentation:<\/strong> Binary Authorization<\/a>)<\/li>\n\n\n\n
- IAM policies per environment<\/li>\n<\/ul>\n\n\n\n
Section 3: Applying site reliability engineering practices to a service (23%)<\/strong><\/h5>\n\n\n\n 3.1 Balancing change, velocity, and reliability of the service. Considerations include:<\/p>\n\n\n\n
\n- Discovering SLIs (e.g., availability, latency) (Google Documentation:<\/strong> Choose your service level indicators (SLIs)<\/a>)<\/li>\n\n\n\n
- Defining SLOs and understanding SLAs (Google Documentation:<\/strong> SRE fundamentals: SLIs, SLAs and SLOs<\/a>)<\/li>\n\n\n\n
- Error budgets (Google Documentation:<\/strong> Concepts in service monitoring<\/a>)<\/li>\n\n\n\n
- Toil automation<\/li>\n\n\n\n
- Opportunity cost of risk and reliability (e.g., number of \u201cnines\u201d)<\/li>\n<\/ul>\n\n\n\n
3.2 Managing service lifecycle. Considerations include:<\/p>\n\n\n\n
\n- Service management (e.g., introduction of a new service by using a pre-service onboarding checklist, launch plan, or deployment plan, deployment, maintenance, and retirement) (Google Documentation:<\/strong> Google Cloud setup checklist<\/a>)<\/li>\n\n\n\n
- Capacity planning (e.g., quotas and limits management) (Google Documentation:<\/strong> Quotas & limits<\/a>)<\/li>\n\n\n\n
- Autoscaling using managed instance groups, Cloud Run, Cloud Functions, or GKE (Google Documentation:<\/strong> Autoscaling groups of instances<\/a>)<\/li>\n\n\n\n
- Implementing feedback loops to improve a service (Google Documentation:<\/strong> Feedback prebuilt component<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.3 Ensuring healthy communication and collaboration for operations. Considerations include:<\/p>\n\n\n\n
\n- Preventing burnout (e.g., setting up automation processes to prevent burnout)<\/li>\n\n\n\n
- Fostering a culture of learning and blamelessness (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n\n\n\n
- Establishing joint ownership of services to eliminate team silos (Google Documentation:<\/strong> Guide to Cloud Billing Resource Organization & Access Management<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.4 Mitigating incident impact on users. Considerations include:<\/p>\n\n\n\n
\n- Communicating during an incident (Google Documentation:<\/strong> Data incident response process<\/a>)<\/li>\n\n\n\n
- Draining\/redirecting traffic (Google Documentation:<\/strong> Enable connection draining<\/a>)<\/li>\n\n\n\n
- Adding capacity (Google Documentation:<\/strong> Scale capacity<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.5 Conducting a postmortem. Considerations include:<\/p>\n\n\n\n
\n- Documenting root causes (Google Documentation:<\/strong> Error Reporting<\/a>)<\/li>\n\n\n\n
- Creating and prioritizing action items<\/li>\n\n\n\n
- Communicating the postmortem to stakeholders (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 4: Implementing service monitoring strategies (21%)<\/strong><\/h5>\n\n\n\n4.1 Managing logs:<\/p>\n\n\n\n
\n- Collecting structured and unstructured logs from Compute Engine, GKE, and serverless platforms using Cloud Logging (Google Documentation:<\/strong> About GKE logs<\/a>, Structured Logging<\/a>)<\/li>\n\n\n\n
- Configuring the Cloud Logging agent (Google Documentation:<\/strong> Configure the Logging agent<\/a>)<\/li>\n\n\n\n
- Collecting logs from outside Google Cloud (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Sending application logs directly to the Cloud Logging API (Google Documentation:<\/strong> Cloud Logging API<\/a>)<\/li>\n\n\n\n
- Log levels (e.g., info, error, debug, fatal) (Google Documentation:<\/strong> View and write Cloud Function logs<\/a>)<\/li>\n\n\n\n
- Optimizing logs (e.g., multiline logging, exceptions, size, cost) (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.2 Managing metrics with Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
\n- Collecting and analyzing application and platform metrics (Google Documentation:<\/strong> Collect metrics overview<\/a>)<\/li>\n\n\n\n
- Collecting networking and service mesh metrics (Google Documentation:<\/strong> Observability overview<\/a>, Cloud Service Mesh overview<\/a>)<\/li>\n\n\n\n
- Use metric explorer for ad hoc metric analysis (Google Documentation:<\/strong> Metrics Explorer<\/a>)<\/li>\n\n\n\n
- Creating custom metrics from logs (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.3 Managing dashboards and alerts in Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
\n- Creating a monitoring dashboard (Google Documentation:<\/strong> Create and manage custom dashboards<\/a>)<\/li>\n\n\n\n
- Filtering and sharing dashboards (Google Documentation:<\/strong> Share a custom dashboard<\/a>)<\/li>\n\n\n\n
- Configuring alerting<\/li>\n\n\n\n
- Defining alerting policies based on SLOs and SLIs (Google Documentation:<\/strong> Creating an alerting policy<\/a>)<\/li>\n\n\n\n
- Automating alerting policy definition using Terraform (Google Documentation:<\/strong> Create alerting policies with Terraform<\/a>, Manage alerting policies with Terraform<\/a>)<\/li>\n\n\n\n
- Using Google Cloud Managed Service for Prometheus to collect metrics and set up monitoring and alerting (Google Documentation:<\/strong> Google Cloud Managed Service for Prometheus<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.4 Managing Cloud Logging platform. Considerations include:<\/p>\n\n\n\n
\n- Enabling data access logs (e.g., Cloud Audit Logs) (Google Documentation:<\/strong> Enable Data Access audit logs<\/a>)<\/li>\n\n\n\n
- Enabling VPC Flow Logs (Google Documentation:<\/strong> Use VPC Flow Logs<\/a>)<\/li>\n\n\n\n
- Viewing logs in the Google Cloud console<\/li>\n\n\n\n
- Using basic versus advanced log filters (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n\n\n\n
- Logs exclusion versus logs export<\/li>\n\n\n\n
- Project-level versus organization-level export<\/li>\n\n\n\n
- Managing and viewing log exports (Google Documentation:<\/strong> Viewing activity logs<\/a>)<\/li>\n\n\n\n
- Sending logs to an external logging platform (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Filtering and redacting sensitive data (e.g., personally identifiable information [PII], protected health information [PHI]) (Google Documentation:<\/strong> De-identifying sensitive data<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.5 Implementing logging and monitoring access controls. Considerations include:<\/p>\n\n\n\n
\n- Restricting access to audit logs and VPC Flow Logs with Cloud Logging (Google Documentation:<\/strong> VPC audit logging information<\/a>)<\/li>\n\n\n\n
- Restricting export configuration with Cloud Logging (Google Documentation:<\/strong> Scenarios for exporting Cloud Logging: Compliance requirements<\/a>)<\/li>\n\n\n\n
- Allowing metric and log writing with Cloud Monitoring (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 5: Optimizing service performance (16%)<\/strong><\/h5>\n\n\n\n5.1 Identify service performance issues:<\/p>\n\n\n\n
\n- Using Google Cloud\u2019s operations suite to identify cloud resource utilization (Google Documentation:<\/strong> Observability in Google Cloud<\/a>)<\/li>\n\n\n\n
- Interpret service mesh telemetry (Google Documentation:<\/strong> The service mesh era<\/a>)<\/li>\n\n\n\n
- Troubleshooting issues with compute resources (Google Documentation:<\/strong> Troubleshooting resource availability errors<\/a>)<\/li>\n\n\n\n
- Troubleshooting deploy time and runtime issues with applications (Google Documentation:<\/strong>
<\/figure>\n<\/div>\n\n\nStep 1 \u2013 Know in-depth about the exam syllabus<\/strong><\/h5>\n\n\n\nBelow mentioned is the detailed course outline for the exam along with the documentation and whitepapers offered by google \u2013<\/p>\n\n\n\n
Topic 1: Bootstrapping a Google Cloud organization for DevOps (17%)<\/strong><\/h5>\n\n\n\n 1.1 Designing the overall resource hierarchy for an organization. Considerations include:<\/p>\n\n\n\n
\n- Projects and folders (Google Documentation:<\/strong> Creating and managing Folders<\/a>)<\/li>\n\n\n\n
- Shared networking (Google Documentation:<\/strong> Shared VPC<\/a>)<\/li>\n\n\n\n
- Identity and Access Management (IAM) roles and organization-level policies (Google Documentation:<\/strong> IAM overview<\/a>)<\/li>\n\n\n\n
- Creating and managing service accounts (Google Documentation:<\/strong> Create a service account<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.2 Managing infrastructure as code. Considerations include:<\/p>\n\n\n\n
\n- Infrastructure as code tooling (e.g., Cloud Foundation Toolkit, Config Connector, Terraform, Helm) (Google Documentation:<\/strong> Config Connector overview<\/a>, Infrastructure as Code on Google Cloud<\/a>)<\/li>\n\n\n\n
- Making infrastructure changes using Google-recommended practices and infrastructure as code blueprints (Google Documentation:<\/strong> Using Recommendations for Infrastructure as Code<\/a>)<\/li>\n\n\n\n
- Immutable architecture (Google Documentation:<\/strong> Best practices for operating containers<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.3 Designing a CI\/CD architecture stack in Google Cloud, hybrid, and multi-cloud environments. Considerations include:<\/p>\n\n\n\n
\n- CI with Cloud Build (Google Documentation:<\/strong> Cloud Build<\/a>, Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- CD with Google Cloud Deploy (Google Documentation:<\/strong> Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- Widely used third-party tooling (e.g., Jenkins, Git, ArgoCD, Packer)<\/li>\n\n\n\n
- Security of CI\/CD tooling (Google Documentation:<\/strong> Building a secure CI\/CD pipeline using Google Cloud built-in services<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.4 Managing multiple environments (e.g., staging, production). Considerations include:<\/p>\n\n\n\n
\n- Determining the number of environments and their purpose (Google Documentation:<\/strong> Create Cloud Composer environments<\/a>)<\/li>\n\n\n\n
- Creating environments dynamically for each feature branch with Google Kubernetes Engine (GKE) and Terraform (Google Documentation:<\/strong> Create a GKE cluster and deploy a workload using Terraform<\/a>, Modern CI\/CD with GKE: Build a CI\/CD system<\/a>)<\/li>\n\n\n\n
- Config Management (Google Documentation:<\/strong> Configurations Overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 2: Building and implementing CI\/CD pipelines for a service (23%)<\/strong><\/h5>\n\n\n\n2.1 Designing and managing CI\/CD pipelines. Considerations include:<\/p>\n\n\n\n
\n- Artifact management with Artifact Registry (Google Documentation:<\/strong> Artifact Registry overview<\/a>)<\/li>\n\n\n\n
- Deployment to hybrid and multi-cloud environments (e.g., Anthos, GKE) (Google Documentation:<\/strong> GKE Multi-Cloud documentation<\/a>, Anthos<\/a>)<\/li>\n\n\n\n
- CI\/CD pipeline triggers (Google Documentation:<\/strong> Cloud Build triggers<\/a>)<\/li>\n\n\n\n
- Testing a new application version in the pipeline (Google Documentation:<\/strong> Test and deploy your application<\/a>)<\/li>\n\n\n\n
- Configuring deployment processes (e.g., approval flows) (Google Documentation:<\/strong> Setting up a CI\/CD pipeline for your data-processing workflow<\/a>)<\/li>\n\n\n\n
- CI\/CD of serverless applications (Google Documentation:<\/strong> Cloud Build<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.2 Implement CI\/CD pipelines:<\/p>\n\n\n\n
\n- Auditing and tracking deployments (e.g., Artifact Registry, Cloud Build, Google Cloud Deploy, Cloud Audit Logs) (Google Documentation:<\/strong> Artifact Registry audit logging<\/a>, Cloud Audit Logs overview<\/a>)<\/li>\n\n\n\n
- Deployment strategies (e.g., canary, blue\/green, rolling, traffic splitting)<\/li>\n\n\n\n
- Rollback strategies (Google Documentation:<\/strong> Rollbacks, gradual rollouts, and traffic migration<\/a>)<\/li>\n\n\n\n
- Troubleshooting deployment issues (Google Documentation:<\/strong> Troubleshooting deployments<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.3 Managing CI\/CD configuration and secrets. Considerations include:<\/p>\n\n\n\n
\n- Secure storage methods and key rotation services (e.g., Cloud Key Management Service, Secret Manager) (Google Documentation:<\/strong> Secret Manager<\/a><\/strong>)<\/li>\n\n\n\n
- Secret management (Google Documentation:<\/strong> Secret Manager<\/a>)<\/li>\n\n\n\n
- Build versus runtime secret injection (Google Documentation:<\/strong> Configure secrets<\/a>, Use secrets from Secret Manager<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.4 Securing the CI\/CD deployment pipeline. Considerations include:<\/p>\n\n\n\n
\n- Vulnerability analysis with Artifact Registry Artifact analysis and vulnerability scanning<\/a>)<\/li>\n\n\n\n
- Binary Authorization (Google Documentation:<\/strong> Binary Authorization<\/a>)<\/li>\n\n\n\n
- IAM policies per environment<\/li>\n<\/ul>\n\n\n\n
Section 3: Applying site reliability engineering practices to a service (23%)<\/strong><\/h5>\n\n\n\n 3.1 Balancing change, velocity, and reliability of the service. Considerations include:<\/p>\n\n\n\n
\n- Discovering SLIs (e.g., availability, latency) (Google Documentation:<\/strong> Choose your service level indicators (SLIs)<\/a>)<\/li>\n\n\n\n
- Defining SLOs and understanding SLAs (Google Documentation:<\/strong> SRE fundamentals: SLIs, SLAs and SLOs<\/a>)<\/li>\n\n\n\n
- Error budgets (Google Documentation:<\/strong> Concepts in service monitoring<\/a>)<\/li>\n\n\n\n
- Toil automation<\/li>\n\n\n\n
- Opportunity cost of risk and reliability (e.g., number of \u201cnines\u201d)<\/li>\n<\/ul>\n\n\n\n
3.2 Managing service lifecycle. Considerations include:<\/p>\n\n\n\n
\n- Service management (e.g., introduction of a new service by using a pre-service onboarding checklist, launch plan, or deployment plan, deployment, maintenance, and retirement) (Google Documentation:<\/strong> Google Cloud setup checklist<\/a>)<\/li>\n\n\n\n
- Capacity planning (e.g., quotas and limits management) (Google Documentation:<\/strong> Quotas & limits<\/a>)<\/li>\n\n\n\n
- Autoscaling using managed instance groups, Cloud Run, Cloud Functions, or GKE (Google Documentation:<\/strong> Autoscaling groups of instances<\/a>)<\/li>\n\n\n\n
- Implementing feedback loops to improve a service (Google Documentation:<\/strong> Feedback prebuilt component<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.3 Ensuring healthy communication and collaboration for operations. Considerations include:<\/p>\n\n\n\n
\n- Preventing burnout (e.g., setting up automation processes to prevent burnout)<\/li>\n\n\n\n
- Fostering a culture of learning and blamelessness (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n\n\n\n
- Establishing joint ownership of services to eliminate team silos (Google Documentation:<\/strong> Guide to Cloud Billing Resource Organization & Access Management<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.4 Mitigating incident impact on users. Considerations include:<\/p>\n\n\n\n
\n- Communicating during an incident (Google Documentation:<\/strong> Data incident response process<\/a>)<\/li>\n\n\n\n
- Draining\/redirecting traffic (Google Documentation:<\/strong> Enable connection draining<\/a>)<\/li>\n\n\n\n
- Adding capacity (Google Documentation:<\/strong> Scale capacity<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.5 Conducting a postmortem. Considerations include:<\/p>\n\n\n\n
\n- Documenting root causes (Google Documentation:<\/strong> Error Reporting<\/a>)<\/li>\n\n\n\n
- Creating and prioritizing action items<\/li>\n\n\n\n
- Communicating the postmortem to stakeholders (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 4: Implementing service monitoring strategies (21%)<\/strong><\/h5>\n\n\n\n4.1 Managing logs:<\/p>\n\n\n\n
\n- Collecting structured and unstructured logs from Compute Engine, GKE, and serverless platforms using Cloud Logging (Google Documentation:<\/strong> About GKE logs<\/a>, Structured Logging<\/a>)<\/li>\n\n\n\n
- Configuring the Cloud Logging agent (Google Documentation:<\/strong> Configure the Logging agent<\/a>)<\/li>\n\n\n\n
- Collecting logs from outside Google Cloud (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Sending application logs directly to the Cloud Logging API (Google Documentation:<\/strong> Cloud Logging API<\/a>)<\/li>\n\n\n\n
- Log levels (e.g., info, error, debug, fatal) (Google Documentation:<\/strong> View and write Cloud Function logs<\/a>)<\/li>\n\n\n\n
- Optimizing logs (e.g., multiline logging, exceptions, size, cost) (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.2 Managing metrics with Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
\n- Collecting and analyzing application and platform metrics (Google Documentation:<\/strong> Collect metrics overview<\/a>)<\/li>\n\n\n\n
- Collecting networking and service mesh metrics (Google Documentation:<\/strong> Observability overview<\/a>, Cloud Service Mesh overview<\/a>)<\/li>\n\n\n\n
- Use metric explorer for ad hoc metric analysis (Google Documentation:<\/strong> Metrics Explorer<\/a>)<\/li>\n\n\n\n
- Creating custom metrics from logs (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.3 Managing dashboards and alerts in Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
\n- Creating a monitoring dashboard (Google Documentation:<\/strong> Create and manage custom dashboards<\/a>)<\/li>\n\n\n\n
- Filtering and sharing dashboards (Google Documentation:<\/strong> Share a custom dashboard<\/a>)<\/li>\n\n\n\n
- Configuring alerting<\/li>\n\n\n\n
- Defining alerting policies based on SLOs and SLIs (Google Documentation:<\/strong> Creating an alerting policy<\/a>)<\/li>\n\n\n\n
- Automating alerting policy definition using Terraform (Google Documentation:<\/strong> Create alerting policies with Terraform<\/a>, Manage alerting policies with Terraform<\/a>)<\/li>\n\n\n\n
- Using Google Cloud Managed Service for Prometheus to collect metrics and set up monitoring and alerting (Google Documentation:<\/strong> Google Cloud Managed Service for Prometheus<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.4 Managing Cloud Logging platform. Considerations include:<\/p>\n\n\n\n
\n- Enabling data access logs (e.g., Cloud Audit Logs) (Google Documentation:<\/strong> Enable Data Access audit logs<\/a>)<\/li>\n\n\n\n
- Enabling VPC Flow Logs (Google Documentation:<\/strong> Use VPC Flow Logs<\/a>)<\/li>\n\n\n\n
- Viewing logs in the Google Cloud console<\/li>\n\n\n\n
- Using basic versus advanced log filters (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n\n\n\n
- Logs exclusion versus logs export<\/li>\n\n\n\n
- Project-level versus organization-level export<\/li>\n\n\n\n
- Managing and viewing log exports (Google Documentation:<\/strong> Viewing activity logs<\/a>)<\/li>\n\n\n\n
- Sending logs to an external logging platform (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Filtering and redacting sensitive data (e.g., personally identifiable information [PII], protected health information [PHI]) (Google Documentation:<\/strong> De-identifying sensitive data<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.5 Implementing logging and monitoring access controls. Considerations include:<\/p>\n\n\n\n
\n- Restricting access to audit logs and VPC Flow Logs with Cloud Logging (Google Documentation:<\/strong> VPC audit logging information<\/a>)<\/li>\n\n\n\n
- Restricting export configuration with Cloud Logging (Google Documentation:<\/strong> Scenarios for exporting Cloud Logging: Compliance requirements<\/a>)<\/li>\n\n\n\n
- Allowing metric and log writing with Cloud Monitoring (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 5: Optimizing service performance (16%)<\/strong><\/h5>\n\n\n\n5.1 Identify service performance issues:<\/p>\n\n\n\n
\n- Using Google Cloud\u2019s operations suite to identify cloud resource utilization (Google Documentation:<\/strong> Observability in Google Cloud<\/a>)<\/li>\n\n\n\n
- Interpret service mesh telemetry (Google Documentation:<\/strong> The service mesh era<\/a>)<\/li>\n\n\n\n
- Troubleshooting issues with compute resources (Google Documentation:<\/strong> Troubleshooting resource availability errors<\/a>)<\/li>\n\n\n\n
- Troubleshooting deploy time and runtime issues with applications (Google Documentation:<\/strong>
1.1 Designing the overall resource hierarchy for an organization. Considerations include:<\/p>\n\n\n\n
- \n
- Projects and folders (Google Documentation:<\/strong> Creating and managing Folders<\/a>)<\/li>\n\n\n\n
- Shared networking (Google Documentation:<\/strong> Shared VPC<\/a>)<\/li>\n\n\n\n
- Identity and Access Management (IAM) roles and organization-level policies (Google Documentation:<\/strong> IAM overview<\/a>)<\/li>\n\n\n\n
- Creating and managing service accounts (Google Documentation:<\/strong> Create a service account<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.2 Managing infrastructure as code. Considerations include:<\/p>\n\n\n\n
- \n
- Infrastructure as code tooling (e.g., Cloud Foundation Toolkit, Config Connector, Terraform, Helm) (Google Documentation:<\/strong> Config Connector overview<\/a>, Infrastructure as Code on Google Cloud<\/a>)<\/li>\n\n\n\n
- Making infrastructure changes using Google-recommended practices and infrastructure as code blueprints (Google Documentation:<\/strong> Using Recommendations for Infrastructure as Code<\/a>)<\/li>\n\n\n\n
- Immutable architecture (Google Documentation:<\/strong> Best practices for operating containers<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.3 Designing a CI\/CD architecture stack in Google Cloud, hybrid, and multi-cloud environments. Considerations include:<\/p>\n\n\n\n
- \n
- CI with Cloud Build (Google Documentation:<\/strong> Cloud Build<\/a>, Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- CD with Google Cloud Deploy (Google Documentation:<\/strong> Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- Widely used third-party tooling (e.g., Jenkins, Git, ArgoCD, Packer)<\/li>\n\n\n\n
- Security of CI\/CD tooling (Google Documentation:<\/strong> Building a secure CI\/CD pipeline using Google Cloud built-in services<\/a>)<\/li>\n<\/ul>\n\n\n\n
1.4 Managing multiple environments (e.g., staging, production). Considerations include:<\/p>\n\n\n\n
- \n
- Determining the number of environments and their purpose (Google Documentation:<\/strong> Create Cloud Composer environments<\/a>)<\/li>\n\n\n\n
- Creating environments dynamically for each feature branch with Google Kubernetes Engine (GKE) and Terraform (Google Documentation:<\/strong> Create a GKE cluster and deploy a workload using Terraform<\/a>, Modern CI\/CD with GKE: Build a CI\/CD system<\/a>)<\/li>\n\n\n\n
- Config Management (Google Documentation:<\/strong> Configurations Overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 2: Building and implementing CI\/CD pipelines for a service (23%)<\/strong><\/h5>\n\n\n\n
2.1 Designing and managing CI\/CD pipelines. Considerations include:<\/p>\n\n\n\n
- \n
- Artifact management with Artifact Registry (Google Documentation:<\/strong> Artifact Registry overview<\/a>)<\/li>\n\n\n\n
- Deployment to hybrid and multi-cloud environments (e.g., Anthos, GKE) (Google Documentation:<\/strong> GKE Multi-Cloud documentation<\/a>, Anthos<\/a>)<\/li>\n\n\n\n
- CI\/CD pipeline triggers (Google Documentation:<\/strong> Cloud Build triggers<\/a>)<\/li>\n\n\n\n
- Testing a new application version in the pipeline (Google Documentation:<\/strong> Test and deploy your application<\/a>)<\/li>\n\n\n\n
- Configuring deployment processes (e.g., approval flows) (Google Documentation:<\/strong> Setting up a CI\/CD pipeline for your data-processing workflow<\/a>)<\/li>\n\n\n\n
- CI\/CD of serverless applications (Google Documentation:<\/strong> Cloud Build<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.2 Implement CI\/CD pipelines:<\/p>\n\n\n\n
- \n
- Auditing and tracking deployments (e.g., Artifact Registry, Cloud Build, Google Cloud Deploy, Cloud Audit Logs) (Google Documentation:<\/strong> Artifact Registry audit logging<\/a>, Cloud Audit Logs overview<\/a>)<\/li>\n\n\n\n
- Deployment strategies (e.g., canary, blue\/green, rolling, traffic splitting)<\/li>\n\n\n\n
- Rollback strategies (Google Documentation:<\/strong> Rollbacks, gradual rollouts, and traffic migration<\/a>)<\/li>\n\n\n\n
- Troubleshooting deployment issues (Google Documentation:<\/strong> Troubleshooting deployments<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.3 Managing CI\/CD configuration and secrets. Considerations include:<\/p>\n\n\n\n
- \n
- Secure storage methods and key rotation services (e.g., Cloud Key Management Service, Secret Manager) (Google Documentation:<\/strong> Secret Manager<\/a><\/strong>)<\/li>\n\n\n\n
- Secret management (Google Documentation:<\/strong> Secret Manager<\/a>)<\/li>\n\n\n\n
- Build versus runtime secret injection (Google Documentation:<\/strong> Configure secrets<\/a>, Use secrets from Secret Manager<\/a>)<\/li>\n<\/ul>\n\n\n\n
2.4 Securing the CI\/CD deployment pipeline. Considerations include:<\/p>\n\n\n\n
- \n
- Vulnerability analysis with Artifact Registry Artifact analysis and vulnerability scanning<\/a>)<\/li>\n\n\n\n
- Binary Authorization (Google Documentation:<\/strong> Binary Authorization<\/a>)<\/li>\n\n\n\n
- IAM policies per environment<\/li>\n<\/ul>\n\n\n\n
Section 3: Applying site reliability engineering practices to a service (23%)<\/strong><\/h5>\n\n\n\n
3.1 Balancing change, velocity, and reliability of the service. Considerations include:<\/p>\n\n\n\n
- \n
- Discovering SLIs (e.g., availability, latency) (Google Documentation:<\/strong> Choose your service level indicators (SLIs)<\/a>)<\/li>\n\n\n\n
- Defining SLOs and understanding SLAs (Google Documentation:<\/strong> SRE fundamentals: SLIs, SLAs and SLOs<\/a>)<\/li>\n\n\n\n
- Error budgets (Google Documentation:<\/strong> Concepts in service monitoring<\/a>)<\/li>\n\n\n\n
- Toil automation<\/li>\n\n\n\n
- Opportunity cost of risk and reliability (e.g., number of \u201cnines\u201d)<\/li>\n<\/ul>\n\n\n\n
3.2 Managing service lifecycle. Considerations include:<\/p>\n\n\n\n
- \n
- Service management (e.g., introduction of a new service by using a pre-service onboarding checklist, launch plan, or deployment plan, deployment, maintenance, and retirement) (Google Documentation:<\/strong> Google Cloud setup checklist<\/a>)<\/li>\n\n\n\n
- Capacity planning (e.g., quotas and limits management) (Google Documentation:<\/strong> Quotas & limits<\/a>)<\/li>\n\n\n\n
- Autoscaling using managed instance groups, Cloud Run, Cloud Functions, or GKE (Google Documentation:<\/strong> Autoscaling groups of instances<\/a>)<\/li>\n\n\n\n
- Implementing feedback loops to improve a service (Google Documentation:<\/strong> Feedback prebuilt component<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.3 Ensuring healthy communication and collaboration for operations. Considerations include:<\/p>\n\n\n\n
- \n
- Preventing burnout (e.g., setting up automation processes to prevent burnout)<\/li>\n\n\n\n
- Fostering a culture of learning and blamelessness (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n\n\n\n
- Establishing joint ownership of services to eliminate team silos (Google Documentation:<\/strong> Guide to Cloud Billing Resource Organization & Access Management<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.4 Mitigating incident impact on users. Considerations include:<\/p>\n\n\n\n
- \n
- Communicating during an incident (Google Documentation:<\/strong> Data incident response process<\/a>)<\/li>\n\n\n\n
- Draining\/redirecting traffic (Google Documentation:<\/strong> Enable connection draining<\/a>)<\/li>\n\n\n\n
- Adding capacity (Google Documentation:<\/strong> Scale capacity<\/a>)<\/li>\n<\/ul>\n\n\n\n
3.5 Conducting a postmortem. Considerations include:<\/p>\n\n\n\n
- \n
- Documenting root causes (Google Documentation:<\/strong> Error Reporting<\/a>)<\/li>\n\n\n\n
- Creating and prioritizing action items<\/li>\n\n\n\n
- Communicating the postmortem to stakeholders (Google Documentation:<\/strong> Postmortem Culture: Learning from Failure<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 4: Implementing service monitoring strategies (21%)<\/strong><\/h5>\n\n\n\n
4.1 Managing logs:<\/p>\n\n\n\n
- \n
- Collecting structured and unstructured logs from Compute Engine, GKE, and serverless platforms using Cloud Logging (Google Documentation:<\/strong> About GKE logs<\/a>, Structured Logging<\/a>)<\/li>\n\n\n\n
- Configuring the Cloud Logging agent (Google Documentation:<\/strong> Configure the Logging agent<\/a>)<\/li>\n\n\n\n
- Collecting logs from outside Google Cloud (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Sending application logs directly to the Cloud Logging API (Google Documentation:<\/strong> Cloud Logging API<\/a>)<\/li>\n\n\n\n
- Log levels (e.g., info, error, debug, fatal) (Google Documentation:<\/strong> View and write Cloud Function logs<\/a>)<\/li>\n\n\n\n
- Optimizing logs (e.g., multiline logging, exceptions, size, cost) (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.2 Managing metrics with Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
- \n
- Collecting and analyzing application and platform metrics (Google Documentation:<\/strong> Collect metrics overview<\/a>)<\/li>\n\n\n\n
- Collecting networking and service mesh metrics (Google Documentation:<\/strong> Observability overview<\/a>, Cloud Service Mesh overview<\/a>)<\/li>\n\n\n\n
- Use metric explorer for ad hoc metric analysis (Google Documentation:<\/strong> Metrics Explorer<\/a>)<\/li>\n\n\n\n
- Creating custom metrics from logs (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.3 Managing dashboards and alerts in Cloud Monitoring. Considerations include:<\/p>\n\n\n\n
- \n
- Creating a monitoring dashboard (Google Documentation:<\/strong> Create and manage custom dashboards<\/a>)<\/li>\n\n\n\n
- Filtering and sharing dashboards (Google Documentation:<\/strong> Share a custom dashboard<\/a>)<\/li>\n\n\n\n
- Configuring alerting<\/li>\n\n\n\n
- Defining alerting policies based on SLOs and SLIs (Google Documentation:<\/strong> Creating an alerting policy<\/a>)<\/li>\n\n\n\n
- Automating alerting policy definition using Terraform (Google Documentation:<\/strong> Create alerting policies with Terraform<\/a>, Manage alerting policies with Terraform<\/a>)<\/li>\n\n\n\n
- Using Google Cloud Managed Service for Prometheus to collect metrics and set up monitoring and alerting (Google Documentation:<\/strong> Google Cloud Managed Service for Prometheus<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.4 Managing Cloud Logging platform. Considerations include:<\/p>\n\n\n\n
- \n
- Enabling data access logs (e.g., Cloud Audit Logs) (Google Documentation:<\/strong> Enable Data Access audit logs<\/a>)<\/li>\n\n\n\n
- Enabling VPC Flow Logs (Google Documentation:<\/strong> Use VPC Flow Logs<\/a>)<\/li>\n\n\n\n
- Viewing logs in the Google Cloud console<\/li>\n\n\n\n
- Using basic versus advanced log filters (Google Documentation:<\/strong> Logging query language<\/a>)<\/li>\n\n\n\n
- Logs exclusion versus logs export<\/li>\n\n\n\n
- Project-level versus organization-level export<\/li>\n\n\n\n
- Managing and viewing log exports (Google Documentation:<\/strong> Viewing activity logs<\/a>)<\/li>\n\n\n\n
- Sending logs to an external logging platform (Google Documentation:<\/strong> Route logs to supported destinations<\/a>)<\/li>\n\n\n\n
- Filtering and redacting sensitive data (e.g., personally identifiable information [PII], protected health information [PHI]) (Google Documentation:<\/strong> De-identifying sensitive data<\/a>)<\/li>\n<\/ul>\n\n\n\n
4.5 Implementing logging and monitoring access controls. Considerations include:<\/p>\n\n\n\n
- \n
- Restricting access to audit logs and VPC Flow Logs with Cloud Logging (Google Documentation:<\/strong> VPC audit logging information<\/a>)<\/li>\n\n\n\n
- Restricting export configuration with Cloud Logging (Google Documentation:<\/strong> Scenarios for exporting Cloud Logging: Compliance requirements<\/a>)<\/li>\n\n\n\n
- Allowing metric and log writing with Cloud Monitoring (Google Documentation:<\/strong> Log-based metrics overview<\/a>)<\/li>\n<\/ul>\n\n\n\n
Topic 5: Optimizing service performance (16%)<\/strong><\/h5>\n\n\n\n
5.1 Identify service performance issues:<\/p>\n\n\n\n
- \n
- Using Google Cloud\u2019s operations suite to identify cloud resource utilization (Google Documentation:<\/strong> Observability in Google Cloud<\/a>)<\/li>\n\n\n\n
- Interpret service mesh telemetry (Google Documentation:<\/strong> The service mesh era<\/a>)<\/li>\n\n\n\n
- Troubleshooting issues with compute resources (Google Documentation:<\/strong> Troubleshooting resource availability errors<\/a>)<\/li>\n\n\n\n
- Troubleshooting deploy time and runtime issues with applications (Google Documentation:<\/strong>
- Interpret service mesh telemetry (Google Documentation:<\/strong> The service mesh era<\/a>)<\/li>\n\n\n\n
- Restricting export configuration with Cloud Logging (Google Documentation:<\/strong> Scenarios for exporting Cloud Logging: Compliance requirements<\/a>)<\/li>\n\n\n\n
- Enabling VPC Flow Logs (Google Documentation:<\/strong> Use VPC Flow Logs<\/a>)<\/li>\n\n\n\n
- Filtering and sharing dashboards (Google Documentation:<\/strong> Share a custom dashboard<\/a>)<\/li>\n\n\n\n
- Collecting networking and service mesh metrics (Google Documentation:<\/strong> Observability overview<\/a>, Cloud Service Mesh overview<\/a>)<\/li>\n\n\n\n
- Configuring the Cloud Logging agent (Google Documentation:<\/strong> Configure the Logging agent<\/a>)<\/li>\n\n\n\n
- Draining\/redirecting traffic (Google Documentation:<\/strong> Enable connection draining<\/a>)<\/li>\n\n\n\n
- Establishing joint ownership of services to eliminate team silos (Google Documentation:<\/strong> Guide to Cloud Billing Resource Organization & Access Management<\/a>)<\/li>\n<\/ul>\n\n\n\n
- Capacity planning (e.g., quotas and limits management) (Google Documentation:<\/strong> Quotas & limits<\/a>)<\/li>\n\n\n\n
- Defining SLOs and understanding SLAs (Google Documentation:<\/strong> SRE fundamentals: SLIs, SLAs and SLOs<\/a>)<\/li>\n\n\n\n
- Binary Authorization (Google Documentation:<\/strong> Binary Authorization<\/a>)<\/li>\n\n\n\n
- Secret management (Google Documentation:<\/strong> Secret Manager<\/a>)<\/li>\n\n\n\n
- Deployment to hybrid and multi-cloud environments (e.g., Anthos, GKE) (Google Documentation:<\/strong> GKE Multi-Cloud documentation<\/a>, Anthos<\/a>)<\/li>\n\n\n\n
- Creating environments dynamically for each feature branch with Google Kubernetes Engine (GKE) and Terraform (Google Documentation:<\/strong> Create a GKE cluster and deploy a workload using Terraform<\/a>, Modern CI\/CD with GKE: Build a CI\/CD system<\/a>)<\/li>\n\n\n\n
- CD with Google Cloud Deploy (Google Documentation:<\/strong> Cloud Build documentation<\/a>)<\/li>\n\n\n\n
- Making infrastructure changes using Google-recommended practices and infrastructure as code blueprints (Google Documentation:<\/strong> Using Recommendations for Infrastructure as Code<\/a>)<\/li>\n\n\n\n
- Shared networking (Google Documentation:<\/strong> Shared VPC<\/a>)<\/li>\n\n\n\n