IT plans to replicate an S3 bucket of property records to a second AWS Region for disaster recovery. Which cost factor should the architect expect to evaluate?
Select an answer to reveal the explanation.
Short Explanation
Moving a copy of the property vault to another Region is like shipping boxes to a second warehouse — the road trip between Regions can show up on the bill. It is not free just because both warehouses are AWS, and Dedicated Hosts or CloudFront invalidations are different cost stories.
Full Explanation
When IT plans to replicate an S3 bucket of property records to a second AWS Region for disaster recovery, the architect should expect to evaluate cross-Region data transfer charges that can apply when data moves between Regions. Cross-Region replication improves geographic resilience for civic records, but bytes leaving one Region toward another are a cost factor in addition to storage in both Regions and request charges. Budgeting only for single-Region storage undercounts DR.
Region copies are not always free, and the cost is not merely the local disk price of an on-premises SAN. EC2 Dedicated Host socket fees do not automatically replace all object storage charges for S3 CRR. CloudFront invalidation fees are not required for every S3 PUT inside one Region and are unrelated to the primary CRR cost driver. Eliminate distractors that invent free replication or swap in unrelated fee types.
Exam caveat: Same-Region versus cross-Region transfer pricing differs. CRR also implies storage duplication costs. CLF expects recognition that multi-Region data movement is not free.
Operational check for property records DR: enable CRR with appropriate IAM roles, estimate monthly change rates for transfer costing, replicate only required prefixes if full-bucket copy is unnecessary, verify objects and encryption in the destination Region, test restore/read failover procedures, and include both Regions' storage in finance forecasts.