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 development team uses local Google Cloud emulators (such as the Cloud Bigtable, Cloud Spanner, Cloud Pub/Sub, and Cloud Firestore emulators) in their CI/CD test pipeline to test application code before deploying to Google Cloud.
During automated CI/CD pipeline runs against the local emulators, all integration and benchmark tests pass without errors. However, after deploying the application to a pre-production staging project connected to live Google Cloud services, the application experiences two critical issues:
Which statement accurately describes the functional discrepancies between local GCP emulators and live managed services that caused these differences?
This option asserts that emulators have an artificial rate limit (100 QPS) that suppresses high-throughput testing and conceals latency anomalies.
Google deliberately built artificial software rate gates into the gcloud emulator binaries to restrict developer performance testing.
Google Cloud Emulators (such as those provided for Cloud Bigtable, Cloud Spanner, Cloud Pub/Sub, and Cloud Firestore) are local, standalone tools designed for rapid functional prototyping, unit testing, and integration testing within development environments and CI/CD pipelines.
FIRESTORE_EMULATOR_HOST or BIGTABLE_EMULATOR_HOST) send plain, unauthenticated gRPC/REST calls, completely masking missing IAM roles (such as roles/datastore.user or roles/pubsub.publisher) or misconfigured credentials.ABORTED error codes.Understanding that emulators provide functional API compatibility rather than performance parity or security parity is essential for cloud architects designing comprehensive multi-stage deployment lifecycles.
This option incorrectly asserts that local emulators synchronize and cache Cloud IAM policies from GCP and that they fail to emulate data-layer features such as database indexing and constraints.
roles/editor, roles/owner, or fine-grained service agent permissions.The emulators functioned as hybrid cloud proxies requiring network connectivity to download IAM policy definitions while running in-memory storage locally.
Concurrency control determines how transactional databases manage simultaneous access to shared documents or table rows, using either optimistic concurrency or pessimistic concurrency.
ABORTED: Too much contention on these documents in production environments.Google Cloud emulators were completely missing transaction APIs and only supported non-transactional batched writes.
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 Validated