Professional Cloud DevOps Engineer Course Notes

Design pipelines for consistent artifact promotion and automated rollback. Immutable artifacts are key for reliable deployments. Manage CI/CD rollouts by monitoring rollout state (progression and status). Promote tested, immutable artifact versions to target environments. Manage pipeline secrets securely using Secret Manager and runtime identity. Secure deployments rely on Binary Authorization, immutable artifacts, and secure artifact storage.

• Mixing different artifact versions across environments.

• Focus on the artifact's journey and the required approvals.

Instrument telemetry with user-visible behavior. Use consistent attributes for correlation. Configure the Ops Agent effectively. Manage logs via Router configuration and bucket retention. Routing filters impact storage – prioritize compliance. Manage Cloud Monitoring alerts effectively: conditions, channels, and runbooks. Analyze distributed traces to identify latency issues. Use trace identifiers and the waterfall to pinpoint problem areas. Troubleshooting starts with the affected service and correlates alerts with changes, metrics, logs, traces, dependencies, and quota state.

• Omitting user-facing attributes leads to poor correlation.

• Think about the data needed to troubleshoot issues effectively.

Design Google Cloud hierarchy using organizations, folders, and projects. Policies inherit, but can be overridden. Manage Google Cloud infrastructure with Terraform, focusing on reproducibility and auditability. CI/CD with Cloud Build: Automate builds from repository triggers. Service Account Security: Limit permissions strictly. Manage multiple environments using Kubernetes Fleets and foundational controls. Secure development relies on Cloud Workstations and a well-defined foundation.

• Confusing organization and folder roles.

• Visualize the hierarchy to understand policy application.

Balance velocity, reliability, and SLOs. Manage service lifecycle – autoscaling, dependencies, availability, redundancy. Mitigating user impact involves rollback and traffic management. Rollbacks require data and operational responses.

• Confusing error budgets with SLOs – they are distinct concepts.

• Think about the impact of changes on SLOs and the error budget.

Collect network performance data with the Performance Dashboard and correlate it with application telemetry for cost optimization. FinOps optimizes cloud costs by aligning resources with business needs.

• Assuming network issues are solely due to network metrics without considering application behavior.

• Understand the interplay between network and application data.