Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A multinational healthcare organization is planning to migrate its patient records to Google Cloud. During a regulatory and compliance review, the legal team establishes two strict governance mandates:
How should the organization categorize these two mandates within its cloud governance framework?
In cloud governance, risk, and compliance, data residency and data sovereignty represent two distinct but complementary levels of control over organizational data. Data residency refers to the physical geographic location where data is stored at rest, driven by national laws, industry regulatory concerns, tax implications, system design objectives, and local culture. Data sovereignty extends beyond physical location to address jurisdictional authority and access control, providing technical mechanisms that prevent the cloud provider or unauthorized parties from accessing customer data without explicit approval.

constraints/gcp.resourceLocations) to restrict where data can be stored and replicated.us-east1 or europe-west1) so data at rest and backups remain within required national boundaries.Distinguishing between data residency and data sovereignty ensures that cloud architects implement the appropriate technical controls for each legal mandate. While regional resource placement satisfies geographic storage laws, maintaining true sovereignty requires additional cryptographic and operational guardrails over data access.
Data classification is a foundational data security practice where an organization defines, identifies, and labels confidential information—such as credit card numbers, addresses, and personally identifiable information (PII)—so that appropriate security controls can be applied. Advanced data residency refers to strict regulatory requirements that govern the geographic location of data while it is actively being processed (in use) or transmitted (in transit), in addition to when it is stored (at rest).
console.us.cloud.google.com), and routing API calls through regional endpoints.This option would be correct if Mandate 1 required using Sensitive Data Protection to discover, classify, and tokenize confidential patient records prior to storage, and Mandate 2 required ensuring that API traffic in transit and runtime processing in use remain strictly within a single geographic region.
This option reverses the foundational definitions of data sovereignty and data residency. While both concepts are essential components of cloud governance, risk, and compliance, they address different legal, regulatory, and technical requirements and cannot be used interchangeably when designing a compliant cloud architecture.
This option would only be correct if Mandate 1 required implementing Cloud External Key Manager (EKM) and Key Access Justifications to prevent provider access to data, and Mandate 2 required using regional selection and constraints/gcp.resourceLocations to keep stored data within a specific country.
A frequent misconception in cloud compliance is assuming that storing data in a domestic Google Cloud region automatically fulfills all data sovereignty requirements. In practice, regional storage satisfies data residency, whereas sovereignty demands explicit technical controls over who can decrypt and access the data.
Software sovereignty and operational sovereignty are specialized pillars of digital sovereignty in Google Cloud that focus on workload portability and provider personnel oversight. Software sovereignty provides assurances that an organization can control the availability of its workloads and run them wherever it wants without being locked into a single cloud provider. Operational sovereignty provides assurances that cloud provider personnel cannot compromise customer workloads, primarily by restricting support and administrative access based on personnel attributes.
This option would be correct if Mandate 1 required deploying workloads using Google Distributed Cloud or multicloud patterns to avoid cloud provider dependency, and Mandate 2 required restricting cloud support interactions strictly to personnel holding specific citizenship status.
Google Cloud organizes digital sovereignty into three pillars: data sovereignty, operational sovereignty, and software sovereignty. Recognizing how these three pillars differ from foundational data residency helps compliance teams map regulatory requirements to the right cloud controls.
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