hardMultiple Select
Cloud Digital Leader Practice Question: Which TWO of the following are important…
Which TWO of the following are important considerations when designing a cloud solution for data residency compliance? (Choose exactly 2.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enabling Cloud Data Residency policies
Option A is correct because enabling Cloud Data Residency policies (such as Google Cloud's Assured Workloads or organization policies that enforce location restrictions) directly constrains where resources and data can be created and stored, which is the core mechanism for meeting data residency requirements. Option B is correct because selecting a Cloud Storage region (for example, europe-west1 or us-central1) determines the physical jurisdiction where the data resides, and data residency compliance specifically requires data to remain within an approved geographic boundary. Option C is not a residency consideration because storage class selection (Standard, Nearline, Coldline, Archive) affects cost and access frequency, not the geographic location of the data. Option D is not a residency consideration because using a single availability zone affects durability and availability, not jurisdictional placement. Option E is not a residency consideration because encryption at rest protects confidentiality but does not control or guarantee where the data is physically stored.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enabling Cloud Data Residency policies
Why this is correct
Cloud Data Residency policies in Microsoft Purview let you restrict data-at-rest storage for Microsoft 365 workloads to a chosen geography, directly satisfying the stem's data residency constraint. They govern where tenant data is stored, not merely where it is processed, making them a core design consideration for compliance.
- ✓
Selecting a Cloud Storage region to store data within required jurisdiction
Why this is correct
Selecting a Cloud Storage region keeps data physically resident within the mandated jurisdiction, directly satisfying the data residency constraint. Because Microsoft Entra ID and cloud services replicate data across regions by default, explicitly pinning storage to an approved geography ensures compliance with legal requirements governing where data may be stored and processed.
- ✗
Choosing the lowest-cost storage class
Why it's wrong here
Cost optimisation selects storage tiers by access frequency and retrieval latency, with no bearing on where data is physically stored or replicated. It becomes relevant when designing lifecycle policies for infrequently accessed blobs, but residency compliance instead demands pinning data to approved geographic regions and verifying replication boundaries.
- ✗
Using a single availability zone for all data
Why it's wrong here
A single availability zone concentrates all data in one physical location, so a zone failure causes total loss and offers no residency benefit; residency concerns where data is stored, not how many zones host it. It is tempting as a cost-saving measure, but it is correct only when resilience is not required.
- ✗
Encrypting all data at rest
Why it's wrong here
Encrypting data at rest protects confidentiality but does not control where data is physically stored or processed, so it cannot satisfy residency obligations. It is tempting because encryption is a core cloud security control, but it is the correct choice when the requirement is protecting data confidentiality rather than constraining its geographic location.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
Learn chapter
Data Lifecycle Management on Google Cloud
Key term
Storage class
A storage class is a category of data storage that defines how data is stored, accessed, retrieved, and billed in a cloud environment.
Key term
Organization
An Organization is a top-level container in Google Cloud that represents your company or entities and serves as the root node for all your cloud resources, policies, and access control.
About these practice questions
Courseiva writes every GCDL question from scratch — 848 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.