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: Tests must run in an isolated environment without requiring outbound internet connectivity or access to live Google Cloud APIs. Pipeline execution must not incur Google Cloud resource usage or API consumption costs. The test framework should interact with standard Google Cloud client libraries without altering the core application codebase. Which strategy should the team implement in their CI pipeline?

Run local Google Cloud emulators for Pub/Sub and Firestore within the CI environment and export the corresponding emulator host environment variables for the test process.: ### What Google Cloud Emulators Are **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. ### How It Meets the Requirements - **No External Connectivity Required**: Emulators run locally within the test container or CI runner as background processes, listening on `localhost` or local container networks without making external network calls. - **Zero Cloud Resource Costs**: All operations execute entirely in local memory or ephemeral local storage, eliminating API request charges and cloud resource billing. - **Unmodified Application Code**: Official **Google Cloud Client Libraries** automatically detect standardized environment variables (such as `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. ### Key Advantages and Capabilities - **Deterministic Testing**: Allows fresh, isolated database and messaging states for every test run by starting and stopping clean emulator instances. - **Fast Execution**: In-memory execution eliminates network latency associated with remote cloud API round-trips. - **Local Authentication Bypass**: Emulators accept dummy credentials, avoiding the security risk of storing live service account keys in CI runners. - **Streamlined CI/CD Integration**: Emulators can be easily packaged into containerized sidecars or background services in tools like Cloud Build, GitHub Actions, or GitLab CI. ### Why This Is Optimal 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.

StudyCerts

Integrate Cloud Emulators In Ci Pipeline | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Integrate Cloud Emulators In Ci Pipeline

Section: Cloud Emulators (e.g., Bigtable, Spanner, Pub/Sub, and Firestore)

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

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:

Tests must run in an isolated environment without requiring outbound internet connectivity or access to live Google Cloud APIs.
Pipeline execution must not incur Google Cloud resource usage or API consumption costs.
The test framework should interact with standard Google Cloud client libraries without altering the core application codebase.

Which strategy should the team implement in their CI pipeline?

Configure Private Google Access and VPC Service Controls around a shared testing VPC to redirect live client API traffic through a private internal endpoint.

Run local Google Cloud emulators for Pub/Sub and Firestore within the CI environment and export the corresponding emulator host environment variables for the test process.

Use Terraform in the CI pipeline to dynamically create live Pub/Sub topics and Firestore databases before testing and run a terraform destroy command after test completion.

Provision a dedicated testing project in Google Cloud, inject service account keys into the CI runner, and run tests against live cloud resources with budget alerts configured.

Professional Cloud Architect

Integrate Cloud Emulators In Ci Pipeline

Related questions