Skip to main content

PCA Certification Preparation Guide: Section 4 — Analyzing and optimizing technical and business processes (~15% of the exam)


Download PDF

This guide helps candidates preparing for the Google Cloud Professional Cloud Architect (PCA) certification explore Section 4 of the exam through the lens of the Tech Equity RAD platform at https://radmodules.dev. Three modules are relevant to this section: GCP Services, which establishes the foundational shared infrastructure; App CloudRun, which deploys serverless containerised applications on Cloud Run; and App GKE, which deploys containerised workloads on GKE Autopilot.

You interact with each module by configuring its variables in the RAD UI deployment portal, then exploring the resulting infrastructure in the GCP Console. This guide maps each exam topic to the relevant variables you can configure and the console locations where you can observe the outcomes. It also highlights PCA objectives that are not currently implemented by these modules, providing guidelines for self-guided research and exploration.

4.1 Analyzing and defining technical processes​

SDLC and Continuous Integration/Continuous Deployment​

Concept: Automating testing, integration, and deployment to improve deployment velocity and reliability.

In the RAD UI:

  • Continuous Integration (CI): The enable_cicd_trigger variable (Group 7) integrates the source repository (github_repository_url) with Cloud Build to compile containers and push them to Artifact Registry.
  • Continuous Deployment (CD): The cloud_deploy_stages variable (Group 7 for Cloud Run, Group 7 for GKE) defines the pipeline stages (e.g., Dev -> Staging -> Prod) orchestrated by Google Cloud Deploy.
  • Testing and Validation: traffic_split (Group 3 for Cloud Run) allows for A/B testing and canary rollouts at the infrastructure layer to validate software safely.

Console Exploration: Navigate to Cloud Build > Triggers to see the CI integration. Navigate to Cloud Deploy > Delivery pipelines to see the CD promotion flow. In Cloud Run, check the Revisions tab to verify traffic splitting.

Real-world example: An engineering team releasing a payments API uses Cloud Build to run unit tests on every pull request merge. On success, Cloud Deploy automatically promotes the container image to the Staging environment. A canary rollout then directs 10% of production traffic to the new revision via traffic_split, and Cloud Monitoring alerts fire if the error rate on the new revision exceeds 0.5% — giving the team automated rollback capability before all users are affected.

💡 Additional Technical Process Objectives & Learning Guidelines​

  • Disaster Recovery: Study the technical processes for implementing Pilot Light, Warm Standby, and Hot Standby (Active-Active) architectures.
  • Troubleshooting/Root Cause Analysis: Understand SRE principles. Differentiate between diagnosing the symptom versus treating the root cause (e.g., using Cloud Profiler for memory leaks).
  • Service Catalog: Explore Google Cloud Service Catalog to understand how administrators curate approved, compliant Terraform or Deployment Manager templates for developers.

4.2 Analyzing and defining business processes​

Change Management and Business Continuity​

Concept: Ensuring organizational checks and balances are enforced during deployments and operations.

In the RAD UI:

  • Change Management: The platform implicitly utilizes Cloud Deploy, which supports manual approval gates before promoting a release to the production stage.
  • Cost Optimization (CapEx/OpEx): As covered in Section 1, configuring serverless scaling bounds (min_instance_count, Group 3) optimizes OpEx compared to static VM CapEx.

Console Exploration: Navigate to Cloud Deploy > Delivery pipelines, click on a release, and observe the "Promote" and "Approve" workflow buttons.

Real-world example: A regulated insurance company requires a change advisory board (CAB) sign-off before any production deployment. Cloud Deploy's manual approval gate enforces this process: a release is automatically promoted from Staging to Pre-Production by CI, but the Production promotion gate requires explicit approval from a designated release manager in the Cloud Deploy console. This creates an auditable, tamper-proof deployment record that satisfies SOC 2 change management controls.

💡 Additional Business Process Objectives & Learning Guidelines​

  • Stakeholder Management & Customer Success: Understand how to facilitate communication between DevOps engineers and business executives, translating technical metrics (latency) into business metrics (ROI, conversion rates).
  • Team Assessment/Skills Readiness: Recognize when a team lacks the skills to manage Kubernetes (GKE) and pivot the architectural design to a lower-overhead platform like Cloud Run.
  • Decision-Making Processes: Understand the concept of "Error Budgets" in SRE to mathematically determine whether a team should focus on feature velocity or stability.