Question

Difficulty: EasyRelational Data Storage Solutions

A company is deploying a new retail application in Azure that requires a relational database backend. The database design must satisfy the following requirements:
- Cost-effectively manage resource allocation for 20 databases that experience short, unpredictable spikes in usage.
- Ensure that database backups remain available even if a single datacenter within the primary region suffers a complete outage.

Which two options should you include in the design? (Select two.)

  1. Azure SQL Database Elastic PoolsAnswer
  2. Zone-redundant storage (ZRS) for backup storage redundancyAnswer
  3. C
    Locally redundant storage (LRS) for backup storage redundancy
  4. D
    Azure SQL Database Single Database deployment for each database

Answer

Azure SQL Database Elastic Pools and Zone-redundant storage (ZRS) for backup storage redundancy.
Azure SQL Database Elastic Pools are the optimal choice to manage resource allocation and cost for multiple databases with unpredictable workloads. Zone-redundant storage (ZRS) provides the required resiliency against a single datacenter outage by replicating backup data across different availability zones within the region.

Step-by-Step Solution

1
Analyze the database resource sharing requirement.
Since there are 20 databases with unpredictable usage spikes, Azure SQL Database Elastic Pools is the most cost-effective choice to share compute resources.
Elastic Pools allow databases to share a pool of resources, preventing the need to over-provision each individual database.
2
Analyze the backup redundancy requirement.
To protect backups against a single datacenter failure within the region, Zone-redundant storage (ZRS) must be chosen.
Locally redundant storage (LRS) stores all copies within a single datacenter, which fails the requirement to survive a datacenter outage.

Key Concept

Azure SQL Database Elastic Pools and Backup Redundancy Options
Rate this question