Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A software engineering team is building an event-driven microservices application that reads from and writes to Google Cloud Pub/Sub and Cloud Firestore. During continuous integration (CI) pipeline executions on self-hosted runners, the team wants to run automated integration tests to validate end-to-end message flows and data persistence logic.
The CI environment has strict operational constraints:
Which strategy should the team implement in their CI pipeline?
This pattern uses Infrastructure as Code (IaC) with Terraform to dynamically provision ephemeral Google Cloud cloud resources for each CI pipeline job and tear them down immediately following test execution.
The team needed to validate Infrastructure as Code definitions, module configurations, and cloud deployment pipelines prior to merging pull requests into production branches.
Google Cloud emulators (such as the Cloud Pub/Sub emulator and Cloud Firestore emulator) are local software instances provided via the Google Cloud CLI and official container images. They replicate the API behavior, in-memory state management, and messaging semantics of Google Cloud services locally without connecting to live cloud backends.
localhost or local container networks without making external network calls.PUBSUB_EMULATOR_HOST=localhost:8085 and FIRESTORE_EMULATOR_HOST=localhost:8080). When these variables are exported, client libraries bypass production authentication checks and redirect all gRPC/REST calls directly to the local emulator endpoints.
Using local emulators directly solves the isolation, cost, and developer-experience challenges of running automated integration tests in CI pipelines while maintaining exact API parity with production services.
Private Google Access allows virtual machine instances inside a Google Cloud Virtual Private Cloud (VPC) to reach Google APIs using private internal IP addresses rather than public internet IPs, while VPC Service Controls establishes security perimeters around cloud resources to prevent data exfiltration.
The requirement was to secure network communication between production workloads running on Compute Engine/GKE and Google APIs to ensure traffic does not traverse the public internet.
This approach configures the CI pipeline to authenticate against real Google Cloud services in a sandbox or dedicated staging Google Cloud project using an Identity and Access Management (IAM) service account key and monitors costs using Cloud Billing budget alerts.
The goal was to perform end-to-end synthetic testing or pre-production staging validation that requires testing real Google Cloud IAM permission boundaries, multi-region replication latency, or live hardware integrations.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated