AZ-305 Designing Microsoft Azure Infrastructure Solutions Exam

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!

Expert

Gauge your current knowledge

Track Readiness

Set Exam Goal

Expert

Gauge your current knowledge

Track Readiness

Set Exam Goal

Recommend a database service tier and compute tier

Design data storage solutions for relational data

Map Workload Requirements to Service and Compute Offerings

Correlating Workload Patterns to Service Tiers

Choosing the right Azure SQL Database tier requires matching your application's needs to the capabilities of each offering. You analyze key workload patterns like transaction volume, concurrency (how many users or processes access the database at once), and I/O throughput (how fast data can be read and written). These patterns directly influence whether you need more compute resources or a specific storage architecture to meet performance goals and SLAs. You also weigh these technical needs against cost constraints, which guide the choice between the vCore and DTU purchasing models. The vCore model lets you select the number of vCores, memory, and storage size independently, while the DTU model provides a bundled set of these resources.

General Purpose Tier

The General Purpose service tier uses a remote storage model where the compute and storage layers are separated. This design makes it cost-effective for workloads that need balanced performance and high availability but do not have strict low-latency demands. It is ideal for general business applications with moderate transaction rates. Within this tier, you can choose between a provisioned compute tier, where you pay for a fixed amount of resources, or a serverless compute tier, which scales compute automatically based on usage and bills you for what you consume. This flexibility helps maintain cost efficiency for applications with variable or predictable loads.

...

A decision tree that guides users from workload requirements to the appropriate Azure SQL Database service tier and compute tier, branching on data volume, latency, and usage predictability.

Business Critical Tier

The Business Critical tier is built for performance and high availability. It delivers consistently low I/O latency by using local SSD storage instead of remote storage. It maintains multiple high availability replicas to provide fast failover and includes a free readable secondary replica for read scale-out workloads, like reporting. This tier suits Online Transaction Processing (OLTP) systems with high transaction volumes and concurrency. When selecting this tier, you must choose appropriate vCore sizes to match your peak performance needs. While it has a higher cost, it offers a higher SLA and advanced features like automatic page repair and zone-redundant availability, making it the choice for mission-critical applications.

Hyperscale Tier

The Hyperscale tier provides a cloud-native architecture with independently scalable compute and storage. It supports massive databases (up to 128 TB) and allows you to dynamically adjust vCores without waiting for lengthy data copy operations. You can also scale out read workloads by adding multiple named replicas. This tier is designed for workloads that outgrow the limits of other tiers, including those with enormous data volumes or mixed OLTP and analytical processing (HTAP). Billing is based on the actual storage used and the provisioned compute, which allows for efficient cost management as the database grows. Hyperscale ensures rapid scaling, fast backup and restore, and high availability for the broadest range of demanding database scenarios.

...

Recommend a solution for storing relational data Recommend a solution for database scalability

AZ-305 Designing Microsoft Azure Infrastructure Solutions Exam

Recommend a database service tier and compute tier

Map Workload Requirements to Service and Compute Offerings

Correlating Workload Patterns to Service Tiers

General Purpose Tier

Azure SQL Database Tier Selection

Business Critical Tier

Hyperscale Tier

Map Workload Requirements to Service and Compute Offerings

Correlating Workload Patterns to Service Tiers

General Purpose Tier

Business Critical Tier

Hyperscale Tier