Venture into the world of Azure Infrastructure, where design meets functionality. Harness your skills and gain mastery over complex cloud structures to ace the AZ-305 Designing Microsoft Azure Infrastructure Solutions exam!
Prepare and test your skills
Prepare and test your skills
A comparison matrix of four Azure Storage redundancy models (LRS, ZRS, GRS, and RA-GRS) evaluated by scope, protection level, read access, and cost. It shows how protection increases from local hardware failures to regional outages as you move from LRS to RA-GRS.
LRS copies your data three times within a single data center, protecting from a hardware failure but not from an entire data center outage. ZRS replicates data across multiple availability zones within the same region, offering protection from a data center failure.
Use RA-GRS when you need read access to your data in the secondary region during a primary region outage, as RA-GRS builds on GRS by allowing read access to the secondary copy. GRS only provides replication to a secondary region without read access, so RA-GRS helps keep an application running during a primary region outage.
In a single-master configuration, one region handles all writes, providing strong consistency but potentially adding write latency. Multi-master allows writes in any of several regions, minimizing write latency and maximizing availability, but requires careful conflict management.
Strong consistency ensures all users see the most recent write immediately, but increases latency. Eventual consistency provides the fastest reads and writes, but allows temporary differences between regions. Bounded staleness and session consistency offer middle-ground options balancing consistency and latency.
Azure Storage provides several built-in redundancy models to protect your data. Locally Redundant Storage (LRS) copies your data three times within a single data center, protecting you from a hardware failure but not from an outage of the entire data center. Zone-Redundant Storage (ZRS) replicates data across multiple data centers, called availability zones, within the same Azure region, offering protection from a data center failure. For protection against a regional disaster, Geo-Redundant Storage (GRS) copies your data to a secondary region hundreds of miles away. Read-Access Geo-Redundant Storage (RA-GRS) builds on GRS by also allowing read access to the data in that secondary region, which can keep an application running during a primary region outage.
Azure Cosmos DB uses a different approach, allowing you to configure how data is replicated across regions based on your needs for writes and consistency. In a single-master configuration, one designated region handles all write operations, while other regions can serve read requests; this provides strong consistency but can add latency for writes. A multi-master configuration allows writes to occur in any of several regions, which minimizes write latency and maximizes availability but requires careful management of potential conflicts. Both models support multi-region replication, which places copies of your data in multiple geographic locations to serve users with low latency.
The choice of replication model directly impacts the balance between data consistency and operation latency. Cosmos DB offers configurable consistency levels to manage this trade-off. Strong consistency ensures all users see the most recent write immediately, but it increases latency. Eventual consistency provides the fastest reads and writes but allows for temporary differences between regions. Bounded staleness and session consistency offer middle-ground options, guaranteeing that data is only out-of-date by a specific time window or is consistent within a single user's session, respectively. The chosen consistency policy determines the performance and data accuracy your application will experience.
Selecting the right redundancy model is key to meeting your Recovery Point Objective (RPO), which defines how much data loss is acceptable, and your Recovery Time Objective (RTO), which defines how long an outage can last. For the lowest RPO and RTO, you need automated failover capabilities and geo-redundancy, such as GRS for Storage or multi-region replication for Cosmos DB. Regularly scheduled snapshots and geo-backups provide a safety net for point-in-time recovery, helping you achieve a specific RPO. The configuration must be tested through failover drills and supported by proactive monitoring with tools like Azure Monitor to ensure the solution works as designed during an actual outage.
StudyCerts
StudyCerts