Multi-region deployment patterns in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Understanding Azure Traffic Manager routing methods

Which Azure Traffic Manager routing method directs user traffic to the endpoint with the lowest network latency?

A Geographic routing

B Priority routing

C Weighted routing

D Performance routing

💡 Hint

Think about which method optimizes for speed by measuring network delays.

Performance routing directs traffic to the endpoint with the lowest latency, improving user experience by reducing response time.

❓ security

intermediate

Securing data replication in multi-region Azure deployments

Which Azure service feature ensures encrypted data replication between regions for Azure Storage accounts?

A Azure Firewall

B Azure Private Link

C Azure Storage Account Geo-Replication with encryption at rest

D Azure Storage Service Encryption (SSE)

💡 Hint

Consider which feature combines replication and encryption for data durability and security.

Geo-Replication with encryption at rest ensures data is encrypted during replication between regions, protecting data confidentiality.

❓ service_behavior

advanced

Failover behavior in Azure SQL Database geo-replication

What happens to the client connection string when a failover occurs in active geo-replication of Azure SQL Database?

A The connection string remains the same, but connections fail until DNS propagates changes

B Clients must manually update the connection string to point to the new primary region

C The connection string automatically updates to the new primary endpoint without client changes

D Failover disables all connections until manual intervention

💡 Hint

Think about how clients know where the primary database is after failover.

The connection string remains the same, but connections fail until DNS propagates changes. Clients do not need to manually update the connection string because Azure SQL Database uses the same logical server name, and DNS updates to point to the new primary after failover.

✅ Best Practice

advanced

Designing multi-region Azure App Service deployments for zero downtime

Which deployment pattern best supports zero downtime during regional failover for Azure App Services?

A Deploy a single App Service in one region and use Azure Front Door for failover

B Deploy identical App Service instances in multiple regions with Traffic Manager using Priority routing

C Deploy App Services in multiple regions with Weighted routing and manual failover

D Deploy App Services in multiple regions with Traffic Manager using Performance routing

💡 Hint

Consider which routing method prioritizes one region but allows automatic failover.

Priority routing sends traffic to the primary region and automatically fails over to secondary regions, enabling zero downtime.

🧠 Conceptual

expert

Impact of eventual consistency in multi-region Cosmos DB deployments

In a multi-region Azure Cosmos DB setup with eventual consistency, what is a possible outcome immediately after a write operation in one region?

A Some regions may temporarily return stale data until replication completes

B All regions instantly reflect the updated data

C Writes are blocked until all regions confirm the update

D Data is lost if a region fails during replication

💡 Hint

Think about how eventual consistency affects data visibility across regions.

Eventual consistency means updates propagate asynchronously, so some regions may show old data briefly after a write.