Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail bank is transitioning its core transactional SQL database from an on-premises data center to a hybrid and multi-cloud architecture. Strict data residency regulations require all customer personally identifiable information (PII) to remain within national borders, where both Google Cloud and a secondary cloud provider operate local regions. The architecture must meet these requirements:
Which architectural strategy should the database team implement?
Cloud Interconnect and Cross-Cloud Interconnect establish dedicated, high-bandwidth private physical circuits between on-premises networks, Google Cloud, and other cloud providers. Keeping both SQL replicas writable during a connectivity loss is an unconstrained active-active configuration intended to keep both sites accepting traffic independently.
Application-layer TLS alone satisfied all security policies without connectivity-layer encryption, and the database used a consensus-based or fenced failover mechanism to prevent concurrent conflicting writes.
A single-region High Availability (HA) database configuration synchronously replicates data between a primary instance and a standby instance in different zones within the same Google Cloud region. Cloud VPN creates encrypted IPsec tunnels over the public internet, and BigQuery Omni is a multicloud analytics service that runs BigQuery compute locally against data stored in AWS or Azure object storage.
The bank only needed zonal resilience within Google Cloud, had modest replication bandwidth suited for internet-based VPNs, and wanted to analyze external object storage datasets in AWS or Azure rather than replicate a live transactional SQL database.
A multi-region deployment distributes data redundantly across multiple geographic regions—often spanning different countries—to survive wide-area disruptions. Bidirectional replication allows two environments to accept writes concurrently, while Direct Peering establishes a direct network path to Google's edge for public Google services.
Regulations permitted cross-border data replication across neighboring countries, the workload used an eventually consistent data model suited for conflict reconciliation, and the connectivity requirement only involved reaching public Google APIs or Google Workspace.
This strategy combines the business continuity multi-cloud pattern with encrypted hybrid and inter-cloud networking. It pairs an on-premises database migration with a primary cloud deployment in Google Cloud and a disaster recovery (DR) replica hosted by a second cloud service provider (CSP) inside the same country, linked through dedicated private interconnects.
Unlike cross-border multi-region deployments, this design obeys national residency laws. Unlike unencrypted interconnects or public internet VPNs, it delivers both deterministic throughput and connectivity-layer encryption while safely guarding SQL transactions against split-brain corruption.
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