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.
An enterprise is designing a continuous integration and automated integration testing pipeline on Google Cloud for its analytics applications. The lead cloud architect needs to establish deployment and test data management guidelines to meet the following requirements:
Which architecture and test data management strategy should you recommend?
Infrastructure as Code (IaC) using declarative tools like Terraform manages cloud resources by defining target end-states in version-controlled configuration files. In test data management, pairing IaC with synthetic dataset generation, data anonymization, and copy-on-write mechanisms like BigQuery table clones allows organizations to validate complex data pipelines in secure, isolated environments.
This solution combines reproducible, drift-free environment provisioning via Terraform with secure, cost-effective test data isolation, satisfying compliance and engineering reliability needs simultaneously.
This pattern manages production cloud infrastructure via Terraform but limits pre-production testing to local container runtimes (such as Docker) using small, static SQL fixtures or mock database engines.
Developers were executing rapid, early-stage unit tests for isolated SQL query syntax on their local workstations prior to committing code to source control.
Manual provisioning relies on operators configuring resources directly through the Google Cloud console or ad-hoc settings. Granting staging service accounts read-only IAM access to production allows test workloads to query live production data directly across project boundaries.
An auditor required external, read-only verification of production metrics without modifying any configurations or running stateful test suites.
gcloud commands to provision staging resources dynamically, and export raw production tables directly into staging Cloud Storage buckets prior to running tests.Imperative shell scripting with gcloud issues sequential command-line calls to provision Google Cloud resources step-by-step. Exporting raw tables dumps unmasked production data into intermediate Cloud Storage buckets for staging consumption.
A team needed a quick, one-off migration script for non-sensitive data where formal environment lifecycle management was not required.
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