# Data Residency

Data residency is the geographic location where data is stored and, when applicable requirements specify it, processed.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/data-residency

> Data residency connects the physical location of data to legal, contractual, and organizational requirements. Cloud architectures must account for primary databases, replicas, backups, logs, and downstream systems because choosing a deployment Region alone does not establish compliance.

Practice exams covering Data Residency: [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Data Residency

Effective data residency requires explicit geographic rules, complete data-flow coverage, enforceable controls, and recovery plans that stay within approved boundaries.

1. **Explicit geographic boundaries**: Define permitted countries, territories, or Regions for each data classification. Distinguish storage requirements from any additional restrictions on processing, access, or transfers.
2. **Complete lifecycle coverage**: Include replicas, backups, snapshots, caches, exports, and deletion workflows in the residency design. A compliant primary database does not compensate for an unauthorized copy elsewhere.
3. **Residency-aware logging**: Map audit, network, host, and application logs from their sources through ingestion, analysis, and archival storage. Check subscription destinations and external security tools because telemetry can contain regulated information.
4. **Layered enforcement and evidence**: Combine organization policies, deployment checks, configuration monitoring, and audit records. Region restrictions alone do not prove that every service operation or downstream transfer respects the required boundary.
5. **Jurisdiction and compliance distinctions**: Evaluate physical location separately from applicable law, contractual commitments, and provider compliance scope. Encryption and provider certifications support a compliance program but do not independently satisfy residency requirements.
6. **Recovery within approved locations**: Choose replication and disaster-recovery destinations that meet the same geographic requirements as production. Where restrictions prevent cross-Region recovery, document the resulting availability and recovery limitations.

## Cloud services for Data Residency

Use AWS Organizations to establish regional guardrails, then configure regional storage and logging destinations that match the approved geography. Amazon S3 can hold application objects and audit archives, while CloudWatch Logs supports operational log ingestion and analysis. CloudTrail supplies AWS activity records, with its collection scope and destination evaluated independently. Review replication, subscriptions, exports, and external integrations across these services to identify transfers outside the boundary. AWS Artifact supports compliance assessment with provider reports and agreements, but configuration evidence and documented data flows are still needed to demonstrate that the workload meets its own requirements.

- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Regional S3 buckets provide explicit storage destinations for application data, audit logs, and archives. Review replication rules, exports, and downstream consumers to ensure that additional copies remain in approved locations.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records AWS account activity and can deliver trail logs to a selected S3 bucket. Evaluate collection scope separately from storage location because a multi-Region trail can consolidate events from different Regions into one destination.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: Service control policies can restrict many operations outside approved Regions across member accounts. Policies using aws:RequestedRegion need careful handling of global services and operations with cross-Region effects; they are not a complete residency guarantee.
- **[AWS Artifact](https://blowstack.com/tools/cloud-services-hub/aws-artifact)**: AWS Artifact provides access to AWS compliance reports and certain agreements that support assessment of provider controls. Review the relevant service and geographic scope alongside customer-specific obligations rather than treating a report as proof that a workload satisfies residency requirements.

## Data Residency exam questions

Real practice exam questions on Data Residency, with the correct answer and its explanation.

### Question 1 (AIF-C01)

**Question:**

A company is auditing the storage locations of AI training datasets inherited from an acquired business. Policy permits storage only in an approved list of AWS Regions. The datasets are stored in Amazon S3, and some buckets have replication enabled. Other processing and data flows have already been verified. Bucket names and tags identify intended locations, but the company needs evidence of the actual locations of the datasets and their replicas. Which approach provides the required evidence?

**Correct answer:** Retrieve each source bucket's configured AWS Region, inspect its replication destinations, and verify the Region of every destination bucket against the approved list.

**Explanation:** The actual Regions of the source and destination buckets establish where these dataset copies are stored. Inspecting replication destinations ensures that the audit covers replicas rather than only the original datasets.

### Question 2 (MLA-C02 (beta))

**Question:**

A healthcare company is migrating a PostgreSQL database that stores patient observations and clinician-provided labels for ML training. The ingestion application uses SQL joins, foreign keys, and transactions that update multiple tables. The company wants a managed database that preserves these capabilities. Compliance requires all database copies and backups to remain in one approved AWS Region. If an Availability Zone fails, the database must recover automatically without losing acknowledged transactions or requiring application-managed failover. Which storage configuration best meets these requirements?

**Correct answer:** Deploy Amazon RDS for PostgreSQL as a Multi-AZ DB instance deployment in the approved Region. Keep automated backups and any snapshot copies in that Region.

**Explanation:** A Multi-AZ DB instance deployment synchronously replicates to a standby in another Availability Zone and provides automatic failover. This protects acknowledged transactions during an Availability Zone failure while preserving PostgreSQL functionality. Keeping database copies and backups in the approved Region satisfies the stated residency requirement.

### Question 3 (SAP-C03)

**Question:**

A pharmaceutical company stores clinical records in Amazon S3 in eu-central-1. Its research team uses an analytics platform hosted outside the European Union. A contractual requirement prohibits clinical records and patient-level query results from leaving eu-central-1. Only outputs produced by a compliance-approved aggregation process may be transferred to the external platform.

The aggregation process suppresses small cohorts and removes patient-level information. Researchers must be able to submit analysis parameters, but must not be able to modify the process or execute arbitrary code with its permissions. Temporary files and failed-job outputs can contain clinical records. Separate controls already prevent cross-Region replication and unauthorized infrastructure changes.

Which architecture meets these requirements?

**Correct answer:** Run the approved aggregation process in eu-central-1 through a broker that accepts only validated analysis parameters. Keep source data and intermediate outputs in buckets inaccessible to the external platform. Publish only successfully validated aggregate outputs to a separate release bucket that the external platform can read.

**Explanation:** This design places the release boundary after the approved aggregation and validation steps. Researchers cannot replace the processing logic or use its permissions for arbitrary execution. Raw records, temporary files, and failed-job outputs remain inaccessible to the external platform, while only approved aggregates can leave the Region.

### Question 4 (CLF-C02)

**Question:**

A financial services company has a contractual requirement to keep customer records, backups, and associated audit logs within one country. Its application runs in an AWS Region in that country, but the proposed disaster recovery plan copies backups and audit logs to a Region outside the country. Which change would satisfy the location requirement while retaining recovery capabilities?

**Correct answer:** Use multiple Availability Zones in the approved Region and retain backups and audit logs using storage configurations verified to keep that data within the country.

**Explanation:** Multiple Availability Zones provide resilience within a Region. Keeping backups and logs in verified, approved locations preserves recovery capabilities without crossing the contractual boundary. The company must assess all copies of the data, not just the primary records.

### Question 5 (SOA-C03)

**Question:**

A company runs a customer portal in eu-central-1. An Amazon CloudFront distribution serves public static assets from an Amazon S3 origin and routes authenticated requests for customer records to an Application Load Balancer origin. CloudFront terminates HTTPS for both types of requests.

A new contract requires all AWS-side processing and caching of customer record contents to occur only in eu-central-1. Public static assets have no geographic restrictions. The company must retain global edge caching for the static assets and HTTPS access to customer records.

Which change should a CloudOps engineer implement to meet these requirements?

**Correct answer:** Serve customer-record requests directly through a separate HTTPS hostname pointing to the load balancer in eu-central-1. Remove the customer-record origin and routing behavior from CloudFront, and retain CloudFront for public static assets.

**Explanation:** Separating the delivery paths keeps customer-record HTTPS processing at the Regional load balancer and application in eu-central-1 while preserving global edge caching for unrestricted static assets. Removing the customer-record route from CloudFront eliminates that global processing path.

### Question 6 (AIP-C01)

**Question:**

A Canadian company runs a generative AI orchestration service in an Amazon VPC in ca-central-1. Before invoking an approved regional foundation model, the service sends regulated text to an on-premises redaction API at 10.60.24.10. Compliance requires both request and response traffic for this API to remain in Canada. Other enterprise traffic must continue using an existing international network hub.

The orchestration instances use subnet 172.22.8.0/24, explicitly associated with route table rt-ai. Relevant routes in rt-ai are:
• 10.60.0.0/16 → a virtual private gateway connected to a domestic AWS Direct Connect path
• 10.60.24.0/24 → a transit gateway whose configured path traverses the international hub

The VPC's main route table already routes 10.60.0.0/16 through the domestic virtual private gateway, but it is not associated with the orchestration subnet. The on-premises router currently routes 172.22.0.0/16 through the international hub. The domestic Direct Connect connection supports bidirectional connectivity for both networks. Security groups, network ACLs, and firewalls permit the API traffic. No additional routes or policy-based routing affect these flows.

Which change meets the compliance requirement while preserving the international hub routes for other enterprise traffic?

**Correct answer:** Replace the 10.60.24.0/24 route in rt-ai with a route to the domestic virtual private gateway. Add an on-premises route for 172.22.8.0/24 through the domestic Direct Connect path.

**Explanation:** The replacement directs API requests through the domestic connection instead of the international hub. The new on-premises /24 route takes precedence over the existing /16 route, ensuring that responses also use the domestic connection. More general routes remain available for other enterprise traffic.

### Question 7 (DEA-C01)

**Question:**

A Canadian company stores customer event records in an Amazon S3 bucket in ca-central-1. An ETL job in us-east-1 reads these records and writes curated records back to ca-central-1. The job stores temporary files and detailed diagnostic logs containing customer identifiers in us-east-1. A separate monitoring system in us-east-1 receives daily aggregate counts that the compliance team has approved as non-sensitive.

A new contractual requirement states that customer records, including intermediate data and logs containing customer identifiers, must be stored and processed only in Canada. The company wants to retain centralized monitoring of the approved aggregate counts. Which change meets these requirements?

**Correct answer:** Move the ETL job, temporary files, and detailed diagnostic logs to ca-central-1. Continue sending only the approved non-sensitive aggregate counts to the monitoring system in us-east-1.

**Explanation:** This keeps processing and every identified stored copy of restricted customer data in Canada, including intermediate files and sensitive logs. The expressly approved non-sensitive aggregate counts can remain in centralized monitoring outside Canada.

### Question 8 (SCS-C03)

**Question:**

A company uses AWS Organizations and operates workloads in eu-central-1 and us-east-1. A security team in a dedicated logging account must centrally archive all read and write management events for regional AWS services across every member account.

Contracts require events generated in eu-central-1 to be delivered and stored only in eu-central-1. Events generated in us-east-1 must be delivered and stored only in us-east-1. These restrictions apply to encrypted copies as well as plaintext records. Cross-account storage is permitted. Global-service events are collected through a separate approved solution and are outside this project's scope.

The company has enabled all organization-trail prerequisites and can configure the required destination permissions. Which logging architecture meets these requirements?

**Correct answer:** Create a single-Region organization trail in each operating Region, with global-service events excluded and all read and write management events enabled. Deliver each trail to an S3 bucket in the logging account in that same Region, without cross-Region replication or forwarding.

**Explanation:** Each organization trail collects the required regional management events across member accounts while delivering them to a destination in the same Region. Centralizing ownership in the logging account does not require centralizing physical storage in one Region. Excluding global-service events preserves the separately defined collection scope.

### Question 9 (SAA-C03)

**Question:**

A Canadian insurance company is deploying a claims-processing application on Amazon EC2. A contract requires claim documents, application data, backups, and logs containing claim information to be stored and processed only in Canada. Encryption does not exempt data from this requirement. The application must continue accepting claims if an entire AWS Region becomes unavailable. The company has verified that both Canada (Central) and Canada West (Calgary) support the required services. Which resource placement strategy meets these requirements?

**Correct answer:** Deploy application capacity in Canada (Central) and Canada West (Calgary), with sufficient capacity and replicated application data to accept claims in either Region. Configure failover between them and keep backups and claim-related logs only in these Canadian Regions.

**Explanation:** Two Canadian Regions provide separate Regional failure boundaries while keeping regulated processing and all specified data copies within Canada. Replicated application data, sufficient capacity, and configured failover allow the surviving Region to continue accepting claims.

## Practice Data Residency in a full exam

Questions on Data Residency in each practice exam, with every answer option and an explanation for each:

- [AIF-C01](https://blowstack.com/practice-exams/aws-certified-ai-practitioner): 11 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 8 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 6 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 5 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 4 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 3 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 3 questions
- [MLA-C02 (beta)](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 2 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 2 questions

## What is Data Residency

Data residency describes where data resides geographically, such as within a country, an economic area, or an approved set of cloud Regions. Requirements can come from legislation, industry rules, customer contracts, or internal policy. Engineers must translate these requirements into explicit boundaries for particular data classes rather than assume that every workload has the same restrictions. For example, a contract might require customer records and associated audit logs to remain within one country while allowing public website assets to be distributed globally.

Residency is related to, but distinct from, data sovereignty and data localization. Sovereignty concerns the laws and jurisdiction applicable to data, while localization generally refers to requirements to keep specified data within a geographic boundary. Physical placement alone does not resolve questions about foreign legal access, remote administration, or international transfers. Privacy laws also do not universally require all personal data to remain in its country of origin; the applicable rules and transfer conditions must be established with legal and compliance teams.

In the cloud, apply residency requirements across the complete data lifecycle. Identify where applications receive and process information, where databases and object stores persist it, and where replicas, snapshots, backups, exports, caches, and analytics outputs go. Select approved Regions and review each service's documented storage and processing behavior. Multiple Availability Zones within a Region can improve availability without introducing cross-Region replication, but their placement must still satisfy the required boundary. Global services, edge caching, support workflows, and third-party integrations need separate assessment.

Logging deserves particular attention because operational telemetry can contain personal information, resource identifiers, request parameters, or application payloads. Identify the required sources, such as cloud API audit events, network flow logs, DNS query logs, operating-system logs, and application logs. Then map each source to its collection Region, ingestion endpoint, storage destination, subscribers, and archive. A workload hosted in an approved Region can still violate a residency policy if its logs are forwarded to a security platform in an unapproved location.

For example, a German-only contractual boundary might require application data, backups, and security logs to use approved resources in the AWS Europe (Frankfurt) Region. A centralized logging account can still be used, provided its storage and processing resources meet that boundary. An AWS CloudTrail multi-Region trail can collect events from multiple Regions into a designated Amazon S3 bucket; its coverage does not mean each event stays in its source Region. Consequently, the log destination and the geographic scope of collection must both be evaluated.

Use preventive controls, deployment validation, and ongoing monitoring together. Organization policies can restrict many operations outside approved Regions, while infrastructure templates can standardize destinations and disable unauthorized replication. In AWS, conditions using aws:RequestedRegion constrain the Region of the requested endpoint, not necessarily every geographic effect of an operation. Global services and cross-Region capabilities require careful exceptions and additional controls. Encryption and access restrictions protect confidentiality but do not change where data resides.

Residency restrictions introduce trade-offs in disaster recovery, service availability, latency, cost, and centralized security analysis. If only one Region is permitted, cross-Region failover may be unavailable unless another location is explicitly approved. Establish recovery objectives that fit the permitted geography, minimize sensitive fields in logs, and validate retention and deletion across copies. Provider compliance reports help assess service controls and their scope, but a provider certification does not automatically make a customer's architecture compliant. The customer remains responsible for selecting appropriate services, configuring data flows, and maintaining evidence that the implemented design meets its requirements.

## Learn Data Residency in lessons

12 short lessons on Data Residency in 9 certification courses.

- AIF-C01: Data Residency: geographic boundaries across the data lifecycle (Premium), https://app.blowstack.com/lessons/data-residency-geographic-boundaries-across-the-data-lifecycle-aif-c01
- MLA-C02 (beta): Data Residency: geographic boundaries for storage (Premium), https://app.blowstack.com/lessons/data-residency-geographic-boundaries-for-storage-mla-c02
- SAP-C03: Data Residency: enforcing geographic data boundaries (Premium), https://app.blowstack.com/lessons/data-residency-enforcing-geographic-data-boundaries-sap-c03
- CLF-C02: Data Residency: geographic boundaries for data (Premium), https://app.blowstack.com/lessons/data-residency-geographic-boundaries-for-data-clf-c02
- SOA-C03: Data Residency: enforcing geographic boundaries (Premium), https://app.blowstack.com/lessons/data-residency-enforcing-geographic-boundaries-soa-c03
- AIP-C01: Data Residency: geographic boundaries for hybrid AI data flows (Premium), https://app.blowstack.com/lessons/data-residency-geographic-boundaries-for-hybrid-ai-data-flows-aip-c01
