Analyzing and optimizing technical and business processes — PCA Practice Quiz

Question 1

A retail company builds container images in a CI pipeline. Currently, each environment (dev, staging, production) rebuilds the image from source using its own environment-specific Dockerfile. The team frequently discovers that code passing all staging tests fails in production due to subtle differences in the built artifacts. As the architect, what change should you recommend to the SDLC process to eliminate these environment-specific defects?

Accepted Answer

Build the image once in CI, store it in Artifact Registry with an immutable digest, and promote that same artifact through dev, staging, and production.

Answer

Add more integration tests in each environment so defects are caught before the image reaches production.

Answer

Standardize on a single base OS image across all environment-specific Dockerfiles while continuing to rebuild in each environment.

Answer

Run production builds on larger machine types to ensure the compiler behaves consistently with staging.

Question 2

A mid-sized company has migrated several projects to Google Cloud. The finance team is frustrated because they only discover budget overruns weeks later when the invoice arrives, and engineering teams have no visibility into their spending until it is too late to react. Leadership wants a process where teams are automatically notified as they approach their monthly spending thresholds, and wants the option to programmatically trigger automated responses (such as capping non-critical workloads) when a threshold is exceeded. Which approach best meets these business process requirements?

Accepted Answer

Configure Cloud Billing budgets with alert thresholds per project, sending notifications via email and publishing to a Pub/Sub topic that can trigger Cloud Functions for automated responses.

Answer

Export detailed billing data to BigQuery and have the finance team run a scheduled monthly query to review spending after each billing cycle closes.

Answer

Set organization policy constraints to hard-limit the number of resources each project can create, preventing any spending above the budget.

Answer

Enable Cloud Monitoring dashboards showing resource utilization and ask engineering leads to manually check them daily for signs of overspending.

Question 3

A large enterprise runs dozens of teams' workloads across several projects in a single Google Cloud organization. The finance department wants to hold each business unit accountable for its actual cloud spend and produce monthly internal invoices per team. Engineering leadership also wants dashboards showing cost trends by application and environment (prod, staging, dev). What is the most effective approach to enable accurate cost allocation and reporting across the organization?

Accepted Answer

Apply a consistent set of resource labels (e.g., team, application, environment) and cost allocation tags, export detailed Cloud Billing data to BigQuery, and build reports and dashboards grouped by those labels.

Answer

Create a separate billing account for every team and manually reconcile spend at the end of each month using exported PDF invoices.

Answer

Rely on the default Cloud Billing reports in the console and filter by project, assigning one project per resource so costs can be traced.

Answer

Enable budgets and budget alerts on each project so finance receives an email whenever a team exceeds its allocated threshold.

Question 4

A financial services company runs a Cloud Build CI/CD pipeline that deploys to production several times a day. An external auditor requires that every production deployment be traceable to a specific approved change request, and that the identity of the approver, the artifact version, and the timestamp be independently verifiable and retained for seven years. The engineering team wants to satisfy this requirement while keeping deployments fully automated where possible. Which approach best meets the audit and process requirements?

Accepted Answer

Introduce a manual approval gate in the release pipeline that records approver identity, then export Cloud Build and Cloud Audit Logs of each deployment to a retention-locked Cloud Storage bucket for the required period.

Answer

Require developers to email a manager before each deployment and keep the email threads in a shared inbox as the audit record.

Answer

Enable verbose logging in Cloud Build and rely on the 400-day default log retention in Cloud Logging to provide the deployment history.

Answer

Grant the auditor the Cloud Build Editor role so they can inspect build triggers and configurations whenever a review is needed.

Question 5

A retail company deploys its customer-facing web application to Google Kubernetes Engine several times per day. After a recent release caused a checkout outage that went undetected until customer complaints arrived, the release engineering team wants a deployment strategy that automatically exposes new versions to a small subset of live traffic, monitors error rates and latency against defined thresholds, and rolls back automatically if metrics degrade—without requiring a full duplicate production environment. Which approach best meets these requirements?

Accepted Answer

Use a canary deployment managed by Cloud Deploy with automated rollback triggered by Cloud Monitoring SLO-based alerting on error rate and latency.

Answer

Provision a full parallel blue-green environment and cut over 100% of traffic to the green environment after manual smoke testing.

Answer

Adopt a recreate deployment strategy that terminates all old pods before starting new ones to guarantee version consistency.

Answer

Deploy all changes directly to production during a nightly maintenance window and rely on daily database backups for recovery.

Question 6

A financial services company has grown from 5 to 40 developers committing to a shared repository. Recently, several production incidents were traced to code merged directly to the main branch without review, and to merges that bypassed the automated test suite. The engineering leadership wants a repeatable technical process that enforces peer review and prevents untested code from reaching main, while minimizing custom tooling. What should the architect recommend?

Accepted Answer

Configure branch protection rules on the main branch requiring at least one approving pull request review and passing CI status checks before merges are permitted.

Answer

Add a nightly Cloud Scheduler job that scans the main branch for commits lacking review metadata and emails the offending developers a warning.

Answer

Grant only senior engineers write access to main and require all other developers to submit patches by email for manual application.

Answer

Move each developer to a separate repository and have a release manager manually cherry-pick approved commits into a central repository weekly.

Question 7

A financial services company runs a fleet of Compute Engine VMs supporting a customer-facing trading platform. Analysis of the last 18 months shows a stable baseline of 40 n2-standard-8 instances running 24/7, with occasional bursts to 65 instances during market volatility. The finance team wants to reduce Compute Engine spend without sacrificing the ability to scale during bursts, and they want the commitment strategy to survive changes in machine family if engineering later re-architects onto a different VM type. Which approach best optimizes cost while preserving flexibility?

Accepted Answer

Purchase spend-based (flexible) committed use discounts covering the baseline compute spend, and let burst capacity run on on-demand pricing.

Answer

Purchase resource-based committed use discounts (CUDs) for 40 n2-standard-8 instances for 3 years, and let burst capacity above the baseline run on on-demand pricing.

Answer

Run the entire fleet, including the baseline, on Spot VMs to maximize discount rates.

Answer

Purchase resource-based CUDs sized for the peak of 65 n2-standard-8 instances for 1 year to guarantee coverage of all usage.

Question 8

A rapidly growing SaaS company hires several new development teams each quarter. Currently, a central operations team manually creates GCP projects, configures networking, applies IAM bindings, and provisions baseline resources for each new team. This process takes days, produces inconsistent configurations, and is becoming a bottleneck. Leadership wants to standardize and accelerate team onboarding while ensuring every new environment complies with organizational security baselines. Which approach best improves this business process?

Accepted Answer

Create standardized, version-controlled infrastructure-as-code templates (e.g., Terraform blueprints) combined with a project factory pipeline that enforces org policies, networking, and IAM baselines automatically.

Answer

Give each new development team Owner role at the organization level so they can self-provision projects and resources without waiting on the operations team.

Answer

Document the manual steps in a detailed runbook and assign additional operations staff to reduce the provisioning backlog.

Answer

Export an existing project's configuration and have the operations team clone it manually for each new team.

Question 9

A retail company deploys a new checkout service to production several times per week, but the business wants to control exactly when new customer-facing features become visible, run limited A/B experiments, and be able to instantly disable a problematic feature without triggering a redeploy or rollback. The engineering team wants to keep their existing CI/CD pipeline that pushes fully tested code to production continuously. Which technical process change best satisfies both the engineering and business requirements?

Accepted Answer

Introduce feature flags so features can be merged and deployed while staying dark, then toggled on, targeted to segments, or disabled at runtime independent of deployments.

Answer

Switch the pipeline to scheduled monthly release windows so the business can approve every batch of features before deployment to production.

Answer

Adopt a blue-green deployment strategy so the business can approve cutover of the entire environment before any feature is exposed.

Answer

Require every new feature to be developed on a long-lived branch that is only merged and deployed once the business signs off on the release date.

Question 10

A software team has a CI/CD pipeline running on Cloud Build. Their integration test suite frequently produces intermittent failures ('flaky tests') that are not caused by real code defects but by timing issues and shared test data collisions when tests run in parallel. Developers have started re-running the pipeline until it passes, which erodes trust in the test results and slows down deployments. As the architect, what should you recommend to improve the reliability and value of the test process?

Accepted Answer

Isolate test data per test run (e.g., ephemeral datasets/namespaces), quarantine identified flaky tests into a separate non-blocking track, and fix their root causes before returning them to the gating suite.

Answer

Configure the pipeline to automatically retry the entire test suite up to three times and mark the build green if any attempt passes.

Answer

Remove the integration tests from the pipeline entirely and rely on manual QA verification before each production release.

Answer

Reduce test parallelism to run all integration tests sequentially so no data collisions can occur, accepting the longer build times.

Question 11

A financial services company running its trading platform on Google Cloud has experienced three major outages in the past quarter. During each incident, engineers spent significant time debating who caused the problem rather than restoring service, and the same root causes reappeared because fixes were never systematically tracked. The VP of Engineering asks the cloud architect to define a troubleshooting and incident-management process that reduces recurrence and improves mean time to resolution. Which approach should the architect recommend?

Accepted Answer

Establish a blameless postmortem process where each significant incident produces a documented root-cause analysis with tracked, prioritized action items, and define severity-based escalation and on-call runbooks.

Answer

Assign a dedicated accountability review board that identifies the responsible engineer for each outage and requires that person to personally implement all remediation before the next release.

Answer

Increase Cloud Monitoring alert thresholds so that fewer alerts fire, reducing the number of incidents that require formal investigation and freeing engineers to focus on feature delivery.

Answer

Require all production changes to route through a weekly change-approval meeting so that leadership manually reviews and signs off on every deployment before it reaches production.

Question 12

An operations team at a financial services company manually executes a 40-step production deployment checklist every two weeks. Deployments frequently run past midnight, and post-deployment incidents are often traced to a step that was skipped or performed out of order under time pressure. Leadership wants to reduce operational toil and improve reliability without immediately re-architecting the applications. As the cloud architect, what should you recommend as the FIRST process improvement?

Accepted Answer

Codify the deployment checklist as an automated pipeline in Cloud Build with defined stages, so each step runs consistently and in the correct order with an auditable record

Answer

Add a second engineer to the deployment shift to double-check each manual step against the checklist before it is executed

Answer

Migrate all applications to Cloud Run so that deployments become fully managed and the checklist is no longer needed

Answer

Move deployments to a weekend maintenance window so engineers are less rushed and less likely to skip steps

Question 13

A software team of 40 engineers currently develops a set of loosely related microservices in a single Git repository. They practice long-lived feature branches that live for weeks, and they frequently experience painful merge conflicts and integration failures discovered only at release time, once per quarter. Leadership wants to reduce integration risk and enable more frequent, safer releases. As the cloud architect advising on the development process, which change to their source-control and integration process should you recommend?

Accepted Answer

Adopt trunk-based development with short-lived branches merged to main at least daily, protected by automated CI that runs on every merge, with releases decoupled via feature flags.

Answer

Split the monorepo into 40 separate repositories, one per engineer, so each person owns their own integration timeline and avoids conflicts.

Answer

Keep long-lived feature branches but add a manual weekly merge-review meeting where senior engineers resolve accumulated conflicts together.

Answer

Freeze all merges for the two weeks before each quarterly release so the codebase stabilizes before integration testing begins.

Question 14

A retail company's on-call engineers are experiencing severe burnout. They receive hundreds of alerts per week from Cloud Monitoring, most triggered by individual metric thresholds (e.g., CPU > 80%, single 500 error) that resolve themselves without customer impact. Leadership asks the architect to redesign the alerting process to reduce noise while ensuring engineers are still paged when customers are genuinely affected. Which approach best addresses this business and technical process problem?

Accepted Answer

Define Service Level Objectives with error budgets and configure alerts based on the burn rate of the error budget, so pages fire only when customer-facing reliability is at risk.

Answer

Raise all metric thresholds (e.g., CPU > 95%) so fewer alerts trigger, and route the remaining alerts to the same on-call rotation.

Answer

Keep all existing threshold alerts but send them to email instead of paging so engineers can review them during business hours.

Answer

Increase the on-call rotation size so each engineer handles fewer alerts, and add a second escalation tier for overflow pages.

Question 15

A retail company recently migrated dozens of workloads to Google Cloud across several projects. The finance team was surprised by a sudden 40% spike in last month's bill, which they discovered only when the invoice arrived. Leadership wants a repeatable business process that surfaces unexpected spending increases quickly—ideally before the billing cycle closes—without requiring engineers to manually inspect every project. Which approach best establishes this process?

Accepted Answer

Enable Cloud Billing budget alerts with threshold rules and turn on cost anomaly detection so stakeholders are notified automatically when spend deviates from expected patterns.

Answer

Schedule a monthly meeting where each team lead manually reviews their project's Billing report and reports variances to finance.

Answer

Export detailed billing data to BigQuery and require the finance analyst to run ad hoc SQL queries at the end of each month.

Answer

Apply committed use discounts across all projects to lock in predictable pricing and eliminate the possibility of cost spikes.

Question 16

A retail company runs a stateful order-management application on Compute Engine behind a global external load balancer, backed by a Cloud SQL for PostgreSQL instance. The engineering team wants to adopt a deployment process that lets them release a new application version with a backward-incompatible database schema change while guaranteeing near-instant rollback if production monitoring detects elevated error rates. Business stakeholders require that customer transactions never be lost during the release and that any rollback take effect within seconds. Which release strategy best satisfies these technical and business requirements?

Accepted Answer

Use an expand-and-contract (backward-compatible) schema migration, deploy the new version to a parallel green environment sharing the same database, and shift traffic via the load balancer with the ability to switch back instantly.

Answer

Perform an in-place rolling update of the instance group and apply the schema change directly to the production database before the new code deploys.

Answer

Provision an entirely separate blue-green stack including a cloned Cloud SQL database, cut all traffic to green, then reconcile the two databases after go-live.

Answer

Take the application offline during a maintenance window, apply the destructive schema change, deploy the new version, and restore service once validation completes.

Question 17

A retail company has been running on Google Cloud for two years. Their FinOps team reports that Compute Engine spending has grown 40% year over year, but application performance dashboards show most production VMs consistently using under 20% CPU and 30% memory. Leadership wants a data-driven, low-risk process to reduce compute waste without impacting availability. Which approach should the cloud architect recommend to systematically identify and act on the savings opportunity?

Accepted Answer

Review the Compute Engine rightsizing recommendations in the Recommender / Active Assist console, validate them against workload metrics, and apply machine-type changes through a controlled change process.

Answer

Immediately migrate all underutilized VMs to the smallest available machine type to guarantee the maximum possible cost reduction.

Answer

Purchase three-year committed use discounts for the entire current fleet to lock in lower pricing before optimizing usage.

Answer

Convert all production VMs to Spot instances since utilization is low and the workloads clearly do not need guaranteed capacity.

Question 18

A retail company runs a microservices application on GKE. Users intermittently report that checkout requests are slow, but the frontend team, cart team, and payment team each insist their service is healthy based on their own dashboards. The architect needs to define a troubleshooting process that pinpoints which service or inter-service call is responsible for the latency across a single request as it traverses multiple services. Which approach best establishes this capability?

Accepted Answer

Instrument all services with distributed tracing using Cloud Trace (OpenTelemetry) so each request is correlated end-to-end and per-span latency is visible across service boundaries.

Answer

Increase the log verbosity to DEBUG on every service and manually correlate timestamps in Cloud Logging when a slow report comes in.

Answer

Add more Cloud Monitoring uptime checks and alerting policies on each individual service's CPU and memory metrics.

Answer

Enable Cloud Profiler on each service to capture CPU and heap usage flame graphs during peak load.

Question 19

A large enterprise has hundreds of developers who frequently request new GCP projects to prototype ideas. The finance and platform teams complain that these ad-hoc sandbox projects have no spending limits, are never cleaned up, and lack ownership visibility, driving unpredictable cost and sprawl. Leadership wants a repeatable business process that lets developers self-serve sandbox environments while keeping costs and lifecycle under control. What should the cloud architect recommend?

Accepted Answer

Establish a self-service provisioning workflow that creates sandbox projects from a standardized template under a dedicated folder, applying budget alerts, spending caps via quotas, mandatory owner labels, and an automated expiry/teardown policy.

Answer

Grant all developers the Project Creator role at the organization level so they can create projects freely, and review the billing report at the end of each quarter.

Answer

Require developers to email the platform team, who manually create each project and manually track ownership and cost in a spreadsheet.

Answer

Consolidate all experimentation into a single shared project so that only one budget needs to be monitored and no lifecycle management is required.

Question 20

A financial services company has repeatedly discovered critical security vulnerabilities in container images only after they were deployed to production, forcing emergency rollbacks and eroding stakeholder confidence. The architecture team wants to embed security checks earlier in the software development lifecycle so that vulnerable code and images are caught before they reach production, without significantly slowing developer velocity. Which approach best addresses this goal?

Accepted Answer

Integrate automated vulnerability scanning of dependencies and container images into the CI pipeline, failing the build when critical vulnerabilities are detected before artifacts are promoted.

Answer

Schedule a weekly manual penetration test of the production environment and file remediation tickets for the development team to address in the next sprint.

Answer

Enable Security Command Center to continuously scan running production workloads and alert the operations team when critical findings appear.

Answer

Require a security architect to manually review every pull request and sign off before any merge to the main branch is permitted.

More PCA practice