Which pair of factors are commonly considered in multi-region deployments?

Which pair of factors are commonly considered in multi-region deployments?

• A. Latency and UI design.
• B. Data replication/latency and regulatory/compliance constraints.
• C. Cost of storage and CPU performance.
• D. Container image size and registry location.

Answer: (B)

In multi-region deployments, the central concerns are how data is replicated across regions and the latency this introduces, alongside the regulatory and compliance requirements that govern where data can reside and how it can move. Data replication choices determine both performance and consistency: choosing synchronous replication can improve immediacy for transactions but may add cross-region latency and risk, while asynchronous replication can reduce latency but may delay visibility of updates across regions. Latency between regions directly shapes user experience and system behavior, influencing where you place data and how you design failover. Regulatory/compliance constraints are what set the rules for data residency, cross-border transfers, and auditability. Some data must stay within a specific region or country, or be subject to particular privacy and security controls. These rules constrain how you replicate data, which regions you can serve, and how you design data access across borders. When you combine these two factors, you address both the technical performance and the legal requirements that define a resilient, lawful multi-region architecture. Choices focusing on UI design or generic resource costs, or on container image specifics, don’t address the distinct regional deployment considerations as directly.

In multi-region deployments, the central concerns are how data is replicated across regions and the latency this introduces, alongside the regulatory and compliance requirements that govern where data can reside and how it can move. Data replication choices determine both performance and consistency: choosing synchronous replication can improve immediacy for transactions but may add cross-region latency and risk, while asynchronous replication can reduce latency but may delay visibility of updates across regions. Latency between regions directly shapes user experience and system behavior, influencing where you place data and how you design failover.

Regulatory/compliance constraints are what set the rules for data residency, cross-border transfers, and auditability. Some data must stay within a specific region or country, or be subject to particular privacy and security controls. These rules constrain how you replicate data, which regions you can serve, and how you design data access across borders. When you combine these two factors, you address both the technical performance and the legal requirements that define a resilient, lawful multi-region architecture.

Choices focusing on UI design or generic resource costs, or on container image specifics, don’t address the distinct regional deployment considerations as directly.