Examkin

Design Business Continuity Solutions

193 questions

All types193Multiple choice98Multiple select87Matching8
Question 1Question →

A retail company plans to migrate its inventory reconciliation service to Azure Virtual Machines. The service must achieve a cumulative virtual machine uptime SLA of 99.99% and must be resilient against the failure of an entire datacenter.

Which virtual machine deployment configuration should you design to satisfy these requirements?

Show answer & explanation

Answer: Deploy the virtual machines across multiple Availability Zones in the same Azure region.

Answer

Deploy the virtual machines across multiple Availability Zones in the same Azure region.
Deploying virtual machines across multiple Availability Zones in the same Azure region guarantees a 99.99% uptime SLA for at least one instance. This architecture ensures that if a single datacenter or zone experiences an outage, instances in the remaining zones continue to operate, meeting both the high availability SLA and the zone-resilience requirement.

Step-by-Step Solution

1
Analyze the service's high availability SLA and resilience requirements.
The target SLA is 99.99% uptime for compute instances, and the architecture must survive a datacenter-level outage.
This establishes the minimum infrastructure boundaries required to design the compute deployment.
2
Evaluate the SLA guarantees of different Azure compute deployment models.
Single-zone Availability Sets provide 99.95% SLA. Multi-zone deployments (deploying VMs across two or more Availability Zones in a region) guarantee 99.99% SLA.
Matching the SLA requirements with Azure SLA documentation determines which architectural options are viable.
3
Assess the susceptibility of each configuration to datacenter failure.
Multi-zone placement distributes VMs across physically separate datacenters with independent power, cooling, and networking. Single-zone placements (including Availability Sets or single-zone Scale Sets) concentrate resources within a single zone.
This ensures the solution provides the necessary resilience to survive a localized datacenter disaster.

Key Concept

Azure Virtual Machine High Availability SLAs and Zonal Redundancy
Estimated Time:1m 30s
Question 2Question →

A logistics company runs a fleet tracking application in the West US 2 region. The application's architecture includes two front-end web server virtual machines named Web-01 and Web-02, and a backend SQL Server database hosted on a single virtual machine named DB-01.

Web-01 and Web-02 both run on Standard SSD disks, each experiencing a continuous write churn of 1.5 MB/s1.5\text{ MB/s}. DB-01 uses three Premium SSD v1 disks:
* OS Disk: 2 MB/s2\text{ MB/s} average write churn
* Data Disk: 12 MB/s12\text{ MB/s} average write churn
* Transaction Log Disk: 56 MB/s56\text{ MB/s} average write churn

You are designing a disaster recovery (DR) solution to the East US region. The solution must meet the following requirements:
* The web servers must have a Recovery Point Objective (RPO) of 1 hour and a Recovery Time Objective (RTO) of 2 hours.
* The database must have an RPO of less than 10 seconds and an RTO of 15 minutes.

Which disaster recovery design should you recommend?

Show answer & explanation

Answer: Configure Azure Site Recovery to replicate Web-01 and Web-02 to the target region, and deploy SQL Server Always On Availability Groups to replicate the database to a target virtual machine in East US.

Answer

Configure Azure Site Recovery to replicate the web servers (Web-01 and Web-02) to the target region, and deploy SQL Server Always On Availability Groups to replicate the database (DB-01) to a target virtual machine in the target region.
The correct design uses Azure Site Recovery to replicate the web tier virtual machines, while using SQL Server Always On Availability Groups to replicate the database tier. This is necessary because Azure Site Recovery has an absolute write churn limit of 54 MB/s54\text{ MB/s} per Premium SSD v1 disk (even with High Churn enabled). DB-01's transaction log disk has a churn of 56 MB/s56\text{ MB/s}, which exceeds this limit and would fail replication. Furthermore, block-level replication through Azure Site Recovery cannot guarantee the sub-10 second RPO required for the database tier, whereas native SQL Server Always On Availability Groups can.

Step-by-Step Solution

1
Analyze the web tier disaster recovery requirements and capabilities.
Web-01 and Web-02 have an RPO of 1 hour and RTO of 2 hours, with 1.5 MB/s1.5\text{ MB/s} churn. This is well within standard Azure Site Recovery (ASR) limits (up to 8 MB/s8\text{ MB/s} for Standard SSD, and typical RPO is minutes, RTO is under 2 hours). Thus, ASR is suitable for the web tier.
To ensure the web tier can fail over within the given RTO/RPO limits using block-level VM replication.
2
Evaluate the database tier VM disk write churn against Azure Site Recovery limits.
DB-01 has a transaction log disk experiencing 56 MB/s56\text{ MB/s} write churn. Azure Site Recovery's maximum support limit for a Premium SSD v1 disk is 20 MB/s20\text{ MB/s} (Standard replication) and 54 MB/s54\text{ MB/s} (High Churn replication). Since 56 MB/s>54 MB/s56\text{ MB/s} > 54\text{ MB/s}, DB-01 cannot be replicated using ASR.
To determine if ASR can support the write-intensive log disk of the database VM.
3
Select the correct database replication method to meet the near-zero RPO and RTO requirements.
A sub-10 second RPO requires native database-level replication. Deploying SQL Server Always On Availability Groups to a target database VM in the destination region ensures database transactions are replicated asynchronously or synchronously with near-zero RPO, completely bypassing ASR's disk churn limitations.
To select a replication technology that satisfies the database's specific RPO/RTO goals and bypasses hypervisor-level storage limits.

Key Concept

Azure Site Recovery limits and hybrid database replication design patterns
Question 3Question →

OmniGene Diagnostics is designing a disaster recovery and business continuity solution for its genomic analysis application. The application writes raw gene sequencing data to an Azure Storage account. The solution must meet the following requirements:

- Protect data against a local datacenter (zone) outage in the primary region with zero data loss.
- Provide a Recovery Point Objective (RPO) of less than 15 minutes for regional outages.
- Provide a Recovery Time Objective (RTO) of less than 1 hour.
- Allow the secondary region application instance to read data immediately during a primary region outage without waiting for a failover.
- Support write operations in the secondary region if a prolonged primary region outage occurs.
- Minimize costs.

Which two configurations should you recommend to meet the requirements? (Select two.)

Select all that apply

Show answer & explanation

Answer: Configure the storage account replication to use read-access geo-zone-redundant storage (RA-GZRS).; Configure the application in the secondary region to direct read requests to the secondary storage endpoint.

Answer

Configure the storage account replication to use read-access geo-zone-redundant storage (RA-GZRS), and configure the application in the secondary region to direct read requests to the secondary storage endpoint.
To satisfy the requirement of zero data loss during a local datacenter (zone) outage in the primary region, the solution must utilize zone-redundant storage in the primary region. This is provided by geo-zone-redundant storage configurations. Furthermore, to read data immediately in the secondary region during an outage without waiting for a failover, read-access must be explicitly enabled on the secondary storage replica (RA-GZRS), and the application must target the secondary storage endpoint.

Step-by-Step Solution

1
Determine the primary region redundancy requirement.
The requirement states that data must survive a local datacenter (zone) outage in the primary region with zero data loss. This requires zone-redundant storage (ZRS) replication in the primary region.
Locally redundant storage (LRS) places all replicas in a single datacenter, whereas ZRS replicates data across three zones to survive a zone outage.
2
Determine the geo-replication and read accessibility requirement.
The solution requires a secondary region copy with less than 15 minutes RPO, and the ability to read from the secondary region immediately during a primary outage without initiating failover. This necessitates Read-Access Geo-Zone-Redundant Storage (RA-GZRS).
Standard GZRS does not allow read access to the secondary region until a failover is initiated, whereas RA-GZRS exposes a read-only secondary endpoint.
3
Identify the application configuration required to use the secondary region replica.
The application connection string or configuration in the secondary region must be updated to target the storage account's secondary endpoint.
During a primary region outage, the primary endpoint is unavailable. The application must point to the secondary endpoint to perform read operations.

Key Concept

Designing Azure Storage replication using RA-GZRS to achieve zone-redundancy in the primary region and read-only secondary access before failover.
Question 4Question →

A financial technology enterprise is designing a global, multi-region traffic routing and failover solution for its payment processing platform deployed in the East US 2 and West Europe regions. The solution must accommodate the following incoming traffic streams:

* Stream 1: HTTPS-based web API traffic requiring SSL termination at the network edge, path-based routing (routing `/charge` and `/refund` requests to different backend pools), and integrated Web Application Firewall (WAF) protection.
* Stream 2: A proprietary, latency-sensitive TCP-based client application communicating over port 90909090. This stream does not support HTTP encapsulation and must be routed to the closest healthy regional endpoint.

Which traffic routing configuration should you recommend to meet these requirements?

Show answer & explanation

Answer: Deploy Azure Front Door to route Stream 1, and configure Azure Traffic Manager to route Stream 2 to regional Standard Load Balancers.

Answer

Deploy Azure Front Door to route Stream 1, and configure Azure Traffic Manager to route Stream 2 to regional Standard Load Balancers.
The correct configuration uses Azure Front Door for the HTTPS-based web API traffic (Stream 1) because Front Door provides global Anycast routing, SSL offloading at the edge, path-based routing, and integrated Web Application Firewall capabilities. For the proprietary TCP-based traffic on port 90909090 (Stream 2), Azure Traffic Manager is the appropriate choice because it works at the DNS layer and is protocol-independent. Traffic Manager resolves DNS queries to the IP address of the closest healthy regional Standard Load Balancer, allowing direct TCP connections over port 90909090 without trying to proxy the traffic through an HTTP-only service.

Step-by-Step Solution

1
Analyze the protocols and routing requirements of Stream 1.
Stream 1 requires HTTPS, SSL termination, WAF, and URL-path routing. This requires a global Layer 7 load balancer.
Only Layer 7 load balancers can inspect the URI path, handle SSL offloading, and apply WAF rules.
2
Select the appropriate service for Stream 1.
Azure Front Door is selected.
Azure Front Door is a global Anycast-based Layer 7 service matching all requirements for Stream 1.
3
Analyze the protocol and routing requirements of Stream 2.
Stream 2 requires custom TCP on port 90909090 with low-latency global routing to regional endpoints.
Since the protocol is non-HTTP TCP, a Layer 7 global routing solution like Azure Front Door cannot be used.
4
Select the appropriate service for Stream 2.
Azure Traffic Manager is selected to resolve DNS requests to regional Standard Load Balancers.
Azure Traffic Manager operates at the DNS level, making it protocol-independent, allowing it to route clients to regional public IPs hosting the TCP service on port 90909090.

Key Concept

Selecting and combining global Azure load balancing services based on layer-specific capabilities (Layer 4 vs. Layer 7) and protocol limitations.
Estimated Time:2m 30s
Question 5Question →

An organization is designing a disaster recovery (DR) solution from the East US region to the West US region for an inventory management system. The system consists of two Web tier VMs (each with a 100 GB100\text{ GB} Premium SSD and a write churn of 0.5 MB/s0.5\text{ MB/s}), two App tier VMs (each with a 128 GB128\text{ GB} Premium SSD and a write churn of 1.5 MB/s1.5\text{ MB/s}), and one Database tier VM running SQL Server on an Azure VM. The Database VM has one OS disk with a write churn of 2 MB/s2\text{ MB/s}, one data disk with a write churn of 8 MB/s8\text{ MB/s}, and one transaction log disk with a write churn of 26 MB/s26\text{ MB/s}. All disks on the Database VM are Premium SSDs. The organization requires a target recovery point objective (RPO) of 15 minutes15\text{ minutes} and a recovery time objective (RTO) of 2 hours2\text{ hours}. Which disaster recovery design should you recommend?

Show answer & explanation

Answer: Replicate the Web and App tier VMs using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the database to a SQL Server instance running on an Azure VM in the West US region.

Answer

Replicate the Web and App tier VMs using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the database to a SQL Server instance running on an Azure VM in the West US region.
The correct design uses Azure Site Recovery to replicate the Web and App tier VMs, while using SQL Server Always On Availability Groups to replicate the database. This is because the Database VM's transaction log disk has a write churn of 26 MB/s26\text{ MB/s}, which exceeds the maximum support limit of 20 MB/s20\text{ MB/s} per Premium SSD disk for Azure Site Recovery (even with the high-churn profile enabled). Utilizing SQL Server Always On Availability Groups bypasses this ASR limitation and ensures the database is replicated with minimal latency, satisfying the 15 minutes15\text{ minutes} RPO and 2 hours2\text{ hours} RTO.

Step-by-Step Solution

1
Analyze the write churn metrics for all disks in the workload.
The Web VMs have a churn of 0.5 MB/s0.5\text{ MB/s} per disk. The App VMs have a churn of 1.5 MB/s1.5\text{ MB/s} per disk. The Database VM has disk churn rates of 2 MB/s2\text{ MB/s} (OS disk), 8 MB/s8\text{ MB/s} (data disk), and 26 MB/s26\text{ MB/s} (transaction log disk). The total Database VM churn is 36 MB/s36\text{ MB/s}.
This step evaluates whether each virtual machine and its individual disks fall within the support limits of Azure Site Recovery.
2
Compare disk write churn rates against Azure Site Recovery capacity limits.
The Web and App tier VMs are within both standard and high churn limits. For the Database VM, the transaction log disk's write churn of 26 MB/s26\text{ MB/s} exceeds the maximum limit of 20 MB/s20\text{ MB/s} per Premium SSD disk supported by Azure Site Recovery (even under the high-churn capability).
This determines that the Database VM cannot be replicated using Azure Site Recovery and requires a different disaster recovery method.
3
Select a disaster recovery replication strategy for the database tier that supports high write churn and meeting the RPO/RTO.
SQL Server Always On Availability Groups running on Azure VMs in the target region support replication of database transaction logs natively and can easily handle a write churn rate of 26 MB/s26\text{ MB/s} while meeting the 15 minutes15\text{ minutes} RPO.
This completes the hybrid design by pairing Azure Site Recovery for the supported tiers with a native database availability solution for the high-churn SQL Server tier.

Key Concept

Azure Site Recovery (ASR) has strict write churn limits per disk (10 MB/s10\text{ MB/s} standard, 20 MB/s20\text{ MB/s} high churn for Premium SSD v1) and per VM. For virtual machines running database engines with write-intensive transaction logs that exceed these limits, database-native replication mechanisms (such as SQL Server Always On Availability Groups) must be used instead of ASR.
Question 6Question →

A logistics company is designing a disaster recovery solution for an application database. The database is currently hosted on Azure SQL Managed Instance. The solution must meet the following requirements:
- Support automatic failover to a secondary region.
- Provide a single connection endpoint for read-write traffic and a separate endpoint that automatically routes read-only reporting queries to the secondary region.
- Keep the Recovery Point Objective (RPO) under 5 seconds.
- Ensure all replication traffic between the primary and secondary instances remains within a private network boundary.

Which solution should you recommend?

Show answer & explanation

Answer: An Azure SQL Managed Instance Failover Group deployed across peered virtual networks, utilizing the read-only listener endpoint for reporting.

Answer

An Azure SQL Managed Instance Failover Group deployed across peered virtual networks, utilizing the read-only listener endpoint for reporting.
The correct solution uses an Azure SQL Managed Instance Failover Group configured across peered virtual networks. Failover Groups support automatic failover, meet the low RPO, and provide two distinct listener endpoints (read-write and read-only). The read-only endpoint automatically routes reporting traffic to the secondary instance, while virtual network peering ensures that all replication traffic remains secure and private.

Step-by-Step Solution

1
Identify the source database service model and HA/DR capabilities.
The workload runs on Azure SQL Managed Instance. This service supports Failover Groups for cross-region disaster recovery and automatic failover, but does not support Active Geo-Replication.
Choosing the correct replication feature is critical since features vary between Azure SQL Database and Azure SQL Managed Instance.
2
Verify read-scale requirements and routing.
Failover Groups provide a read-write listener and a read-only listener. The read-only listener automatically routes traffic to the secondary replica without needing connection string changes in the main application.
This satisfies the requirement to route reporting queries to the secondary region using a dedicated endpoint.
3
Determine the network security configuration.
Configuring virtual network peering between the virtual networks hosting the primary and secondary Managed Instances allows private traffic routing over the Azure backbone.
This satisfies the security requirement to keep replication traffic within a private network boundary.

Key Concept

Azure SQL Managed Instance Failover Groups
Question 7Question →

An organization needs to set up a backup strategy for their Azure Virtual Machines hosting development and testing workloads. The design must meet the following requirements:
- Minimize storage costs for the backup data.
- Retain daily backups for 30 days.
- Provide the fastest possible restore speed for the last 5 days of backups.

Which of the following configurations should you include in the backup design? (Select TWO).

Select all that apply

Show answer & explanation

Answer: A Recovery Services vault configured with Locally Redundant Storage (LRS); A backup policy with the instant restore retention range set to 5 days

Answer

To meet the requirements of minimizing costs and allowing rapid restore for the last 5 days, you should configure the Recovery Services vault with Locally Redundant Storage (LRS) and set the instant restore retention range to 5 days in the backup policy.
For non-production development environments, minimizing costs is achieved by using Locally Redundant Storage (LRS). Rapid restores are achieved by keeping snapshots on local disk using the instant restore feature, which is limited to a maximum retention of 5 days.

Step-by-Step Solution

1
Select the backup storage redundancy option that minimizes cost.
Choose Locally Redundant Storage (LRS) because it is the cheapest storage replication option for the Recovery Services vault.
LRS keeps three copies of the data within a single datacenter, which is sufficient for non-production environments and reduces costs compared to zone-redundant or geo-redundant storage.
2
Determine the configuration to achieve the fastest restore speed for the most recent 5 days of backups.
Configure the backup policy's instant restore retention to 5 days.
This retains the backup snapshots on the local disk tier for 5 days, allowing fast, disk-level restore operations instead of copying data from the vault.
3
Verify retention limitations for daily recovery points.
Keep the remaining 25 days of recovery points in the vault tier by setting the total retention to 30 days.
Instant restore snapshots cannot be kept for 30 days due to the 5-day limit, so the rest of the 30-day period must use vault-tier storage.

Key Concept

Configuring Recovery Services vault storage redundancy and backup policy instant restore limitations
Estimated Time:1m 0s
Question 8Question →

An organization hosts its production workloads on Azure Virtual Machines. You are designing an Azure Backup solution that must meet the following requirements:
- Technical recoveries of backups from the last 55 days must achieve the lowest possible Recovery Time Objective (RTO) by restoring directly from local disk snapshots.
- Monthly backups must be retained for 33 years (3636 months) to satisfy regulatory auditing compliance.
- The backup data must remain accessible even in the event of an entire Azure region outage.

You deploy a Recovery Services vault configured with Geo-Redundant Storage (GRS). Which configuration should you recommend in the backup policy?

Show answer & explanation

Answer: A backup policy with an instant restore snapshot retention of 55 days, and a long-term retention configuration that keeps monthly recovery points in the vault for 3636 months.

Answer

A backup policy with an instant restore snapshot retention of 55 days, and a long-term retention configuration that keeps monthly recovery points in the vault for 3636 months.
The correct configuration uses an instant restore retention of 55 days to meet the low RTO requirement by restoring directly from local disk snapshots, while keeping the monthly recovery points in the vault for 3636 months to satisfy regulatory compliance. It utilizes GRS to ensure regional resilience.

Step-by-Step Solution

1
Analyze RTO requirements for recent backups.
The requirement states recoveries of backups from the last 55 days must restore directly from local disk snapshots. This is achieved by setting the operational tier (instant restore) retention to 55 days.
Azure Backup's instant restore feature retains snapshots on the VM's disks for 11 to 55 days under a standard policy, allowing direct restorations without copying data from the vault.
2
Analyze long-term compliance retention requirements.
The monthly backups must be kept for 3636 months. This long-term retention should be stored in the vault tier, not as local disk snapshots, to control costs.
Keeping snapshots on managed disks for 3636 months is not supported by Azure Backup policy limits, and storing them on standard/premium SSDs would incur extreme storage costs.
3
Determine the vault resilience configuration.
Confirm that the Recovery Services vault is configured with Geo-Redundant Storage (GRS) as deployed.
GRS replicates backup data to a secondary paired region, ensuring that the backups remain accessible even if the primary region experiences a complete outage.

Key Concept

Azure Backup operational tier (instant restore) vs. vault tier configuration
Estimated Time:2m 0s
Question 9Question →

You are designing a business continuity and disaster recovery solution for a suite of critical Azure Virtual Machines hosting an enterprise resource planning (ERP) application.

The solution must satisfy the following technical and compliance requirements:
1. Operational recovery: Must support instant recovery of VMs directly from local snapshots for any recovery points created within the last 14 days.
2. Compliance retention: Backups must be retained in vault storage for 365 days.
3. Regional resiliency: Backups must be replicated to a secondary paired region. Administrators must be able to perform test restores in the secondary region at any time, including when the primary region is fully operational.

Which vault type, storage redundancy, and backup policy configuration should you recommend?

Show answer & explanation

Answer: A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross Region Restore (CRR) enabled, using an Enhanced backup policy with the instant restore retention set to 14 days.

Answer

A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross Region Restore (CRR) enabled, using an Enhanced backup policy with the instant restore retention set to 14 days.
The correct configuration uses a Recovery Services vault (which is the correct vault type for Azure Virtual Machines) configured with Geo-Redundant Storage (GRS) and Cross Region Restore (CRR) enabled, allowing read/restore access to the secondary region at all times. Additionally, it specifies an Enhanced backup policy to accommodate the 14-day instant restore snapshot retention requirement, which exceeds the 5-day limit of Standard backup policies.

Step-by-Step Solution

1
Determine the correct vault type for Azure Virtual Machine backups.
Identify that Recovery Services vaults are required for Azure VM backups, eliminating options that use Backup vaults.
Azure Backup uses Recovery Services vaults for VMs, SQL Server/SAP HANA on VMs, and Azure Files, while Backup vaults are used for newer workloads like Azure Disks, Blobs, and PostgreSQL.
2
Determine the required vault storage redundancy and restore capabilities.
Identify that Geo-Redundant Storage (GRS) with Cross Region Restore (CRR) is required, eliminating Locally Redundant Storage (LRS).
To satisfy the requirement of performing test restores in the secondary region at any time (even when the primary region is healthy), Cross Region Restore must be enabled, which requires GRS.
3
Determine the backup policy sub-type and parameters required to meet the retention criteria.
Identify that an Enhanced backup policy is required to support a 14-day instant restore retention window.
Standard backup policies only support keeping instant restore snapshots for 1 to 5 days. To keep snapshots for 14 days (which are used for instant recovery), an Enhanced policy is needed as it supports up to 30 days of instant restore retention.

Key Concept

Azure Backup Vault Selection, Policy Tiers, and Redundancy Options
Estimated Time:3m 0s
Question 10Question →

You are designing a backup solution for a fleet of Azure Virtual Machines running a business-critical enterprise resource planning (ERP) application.

The design must satisfy the following requirements:
- Restore operations for backups younger than 7 days must achieve the lowest possible Recovery Time Objective (RTO) by recovering directly from local snapshots (Instant Restore).
- Recovery points must be retained in a Recovery Services vault for 365 days to meet regulatory compliance.
- The solution must allow restoration to a paired secondary region at any time, even if the primary region is fully functional and online.

Which backup configuration should you recommend?

Show answer & explanation

Answer: Configure a Recovery Services vault with Geo-redundant storage (GRS) and Cross Region Restore enabled. Define an Enhanced backup policy with an instant restore retention of 7 days and a vault retention of 365 days.

Answer

Configure a Recovery Services vault with Geo-redundant storage (GRS) and Cross Region Restore enabled, and define an Enhanced backup policy with an instant restore retention of 7 days and a vault retention of 365 days.
The correct configuration uses Geo-redundant storage (GRS) combined with Cross Region Restore (CRR) to satisfy the requirement of restoring to a paired secondary region at any time. Furthermore, because the low-RTO operational recovery requirement spans 7 days, an Enhanced backup policy must be used since the Standard backup policy type enforces a maximum limit of 5 days for local instant restore snapshots.

Step-by-Step Solution

1
Analyze the regional resilience and availability requirements.
Since backups must be restorable to a paired secondary region at any time even when the primary region is fully functional, Geo-redundant storage (GRS) with Cross Region Restore (CRR) must be enabled on the Recovery Services vault.
Standard GRS only allows restoration in the secondary region after Azure declares a disaster and initiates a failover. Enabling CRR allows the customer to perform restores in the secondary region at any time.
2
Determine the backup policy type needed to meet the Recovery Time Objective (RTO) requirement.
An Enhanced backup policy is required because the instant restore retention must be set to 7 days.
The Standard backup policy only supports instant restore (snapshot) retention between 1 and 5 days. The Enhanced backup policy supports snapshot retention up to 30 days, allowing the 7-day low RTO requirement to be met.
3
Evaluate long-term retention requirements.
Set the vault retention to 365 days in the Enhanced backup policy.
This satisfies the regulatory compliance requirement to retain recovery points for one year.

Key Concept

Azure VM Backup Policy Types and Vault Storage Redundancy Options
Question 11Question →

You are designing a high availability and disaster recovery (HA/DR) solution for an on-premises database that is migrating to Azure. The database relies on SQL Server Agent jobs and performs cross-database queries. The disaster recovery design must support automatic failover to a secondary region, a Recovery Time Objective (RTO) of 1 hour, and a single connection endpoint that redirects application traffic without requiring connection string modifications during a failover. Which solution should you recommend?

Show answer & explanation

Answer: Azure SQL Managed Instance configured with a failover group

Answer

Azure SQL Managed Instance configured with a failover group
The correct answer is Azure SQL Managed Instance configured with a failover group. Azure SQL Managed Instance supports features required for legacy SQL Server migrations, including SQL Server Agent and cross-database queries. Configuring it with a failover group enables automatic failover to a secondary region and provides a read-write listener endpoint, allowing the application to connect using a single connection string that automatically redirects traffic during failover.

Step-by-Step Solution

1
Analyze the database compatibility and feature requirements.
The database requires SQL Server Agent and cross-database queries, which rules out Azure SQL Database single database and points to Azure SQL Managed Instance or SQL Server on Azure VMs.
Azure SQL Database single database does not support SQL Server Agent or cross-database queries.
2
Evaluate the HA/DR requirements.
The solution must support automatic failover to a secondary region with a single listener endpoint.
This eliminates configurations that require manual failover and application connection string changes.
3
Verify storage and performance requirements.
SQL Server on Azure VMs with Standard HDD is eliminated due to inadequate performance for database transaction logs.
Standard HDD is unsuitable for database transaction logs, which require low latency and high IOPS provided by Premium SSD or Ultra Disk.

Key Concept

Designing relational database HA and DR using failover groups and choosing the correct Azure SQL service tier based on application compatibility.
Question 12Question →

You are designing a backup solution for production Azure Virtual Machines. The solution must meet the following requirements:
- Operational restores for failures occurring within the last few days must have a Recovery Time Objective (RTO) of under 10 minutes by utilizing the Instant Restore feature.
- The solution must minimize operational costs by using a standard backup policy rather than an enhanced backup policy.
- All backup data must remain within the primary region to comply with local data residency regulations.

What is the maximum retention period in days that can be configured for the instant recovery snapshots in the standard backup policy?

Show answer & explanation

Answer: 5

Answer

5
The correct answer is 5. For standard Azure VM backup policies, the Instant Restore feature keeps snapshots locally for a range of 1 to 5 days (defaulting to 2 days). This meets the low RTO requirement for recent backups while staying within the standard policy constraints to minimize cost.

Step-by-Step Solution

1
Identify the constraints and backup policy type specified in the design scenario.
The scenario requires using a standard backup policy to minimize costs, and calls for sub-10-minute RTO restores utilizing the Instant Restore feature.
This establishes that the retention limits for the standard backup policy's snapshot tier must be evaluated.
2
Determine the maximum configuration limit for instant restore snapshots in a standard policy.
The standard backup policy supports instant restore snapshot retention only between 1 and 5 days, whereas the enhanced policy supports up to 30 days.
Because the standard policy must be used, the maximum value that can be configured is 5 days.

Key Concept

Azure Backup Virtual Machine policy tiers and Instant Restore limits
Question 13Question →

You are designing a disaster recovery (DR) solution for a critical financial application migrating to Azure. The application database has the following requirements:
- Employs native cross-database queries and relies heavily on SQL Server Agent jobs.
- Requires database replication between East US (primary) and West US (secondary).
- The write workload must connect via a single endpoint that remains unchanged during a failover.
- Reporting applications must run read-only queries against the secondary region using a dedicated endpoint.
- All database traffic must remain within private virtual networks without traversing the public internet.

Which database configuration should you recommend to meet these requirements?

Show answer & explanation

Answer: Deploy a primary Azure SQL Managed Instance in East US and a secondary Azure SQL Managed Instance in West US. Configure an Auto-Failover Group between the instances and connect the application using the failover group's read-write and read-only listener endpoints.

Answer

Deploy a primary Azure SQL Managed Instance in East US and a secondary Azure SQL Managed Instance in West US. Configure an Auto-Failover Group between the instances and connect the application using the failover group's read-write and read-only listener endpoints.
The correct solution involves deploying Azure SQL Managed Instance in both regions and linking them via an Auto-Failover Group. SQL Managed Instance provides the necessary SQL Server features (SQL Server Agent and cross-database queries) required for legacy application migration. The Auto-Failover Group supplies a read-write listener endpoint and a read-only listener endpoint, satisfying the requirement for an unchanged client connection string for writes and a dedicated endpoint for reporting workloads. Because SQL Managed Instances are deployed directly within Azure Virtual Networks, the entire configuration maintains private network isolation.

Step-by-Step Solution

1
Evaluate application requirements for database features.
The requirement for native cross-database queries and SQL Server Agent jobs rules out Azure SQL Database (Single Database or Elastic Pool) and points to Azure SQL Managed Instance or SQL Server on Azure VMs.
Azure SQL Database does not support these features natively.
2
Evaluate endpoint requirements for HA/DR.
The requirement for a single unchanged endpoint for writes and a dedicated endpoint for reads points to Auto-Failover Groups, which provide read-write and read-only listener endpoints.
Active geo-replication or SQL VM configurations without additional routing components (like distributed network names or load balancers) do not natively offer these endpoints without connection string changes.
3
Assess storage performance constraints.
Standard HDD is rejected for hosting transaction logs.
Database transaction logs require low-latency and high-IOPS storage (Premium SSD or Ultra Disk) to function correctly under production workloads.

Key Concept

Selecting the correct Azure relational database service and configuring high availability/disaster recovery with Auto-Failover Groups to support legacy SQL Server features and read-scale listeners over private networks.
Estimated Time:3m 0s
Question 14Question →

You are designing an Azure Backup solution for a suite of critical Azure Virtual Machines hosting a high-performance SAP HANA database. The solution must satisfy the following requirements:
- Back up the virtual machines 22 times per day to protect against database transaction losses.
- Retain the local instant recovery snapshots on the virtual machines' managed disks for 1414 days to allow quick operational restores.
- Protect the backup data against regional disasters by replicating it to a secondary paired region, allowing recovery even if the primary region is completely unavailable.

Which of the following configuration options must you include in your backup design? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Configure a Recovery Services Vault with Geo-Redundant Storage (GRS) and enable Cross-Region Restore (CRR).; Create an Enhanced backup policy with a twice-daily backup schedule and set the instant restore retention to 1414 days.

Answer

To meet the requirements, the design must use a Recovery Services Vault configured with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled, combined with an Enhanced backup policy scheduled for twice-daily backups and 1414 days of instant restore retention.
The correct strategy requires configuring a Recovery Services Vault with Geo-Redundant Storage (GRS) and enabling Cross-Region Restore (CRR) to satisfy regional resilience and failover capabilities. Additionally, an Enhanced backup policy must be configured because a Standard policy cannot support the required twice-daily backup schedule or the 1414 days of instant restore snapshot retention.

Step-by-Step Solution

1
Evaluate the backup frequency and operational recovery requirements.
The requirements dictate twice-daily backups and local snapshot retention of 1414 days.
This determines whether a Standard or Enhanced backup policy is needed based on policy limits.
2
Select the appropriate backup policy type.
Select an Enhanced backup policy.
Standard backup policies support only one backup per day and limit instant recovery retention to between 11 and 55 days, whereas Enhanced policies support multiple daily backups and up to 3030 days of instant recovery retention.
3
Determine the vault storage redundancy and restore features.
Configure a Recovery Services Vault with Geo-Redundant Storage (GRS) and enable Cross-Region Restore (CRR).
GRS ensures replication to the paired region, and CRR allows immediate restore operations in the secondary region if the primary region goes offline.

Key Concept

Azure VM Backup Policy Tiers and Vault Redundancy Configurations
Question 15Question →

An organization is designing a backup solution for business-critical Azure Virtual Machines hosting an enterprise database. The solution must meet the following requirements:

* Daily backups must be retained for a minimum of 3030 days.
* Restore operations for any backup up to 1414 days old must be performed as an 'Instant Restore' to meet strict Recovery Time Objective (RTO) targets.
* Backups must remain available even in the event of a regional datacenter disaster.

Which two configurations should you include in the backup design to meet the requirements?

Select all that apply

Show answer & explanation

Answer: Configure an Enhanced backup policy and set the snapshot retention for instant restore to 1414 days.; Create a Recovery Services vault and configure its storage replication to Geo-Redundant Storage (GRS).

Answer

Configure an Enhanced backup policy with 1414 days of snapshot retention for instant restore, and create a Recovery Services vault configured with Geo-Redundant Storage (GRS).
The correct design requires a Recovery Services vault configured with GRS to ensure regional resilience, and an Enhanced backup policy configured with 1414 days of snapshot retention to support instant restore for that duration, as Standard policies only support up to 55 days.

Step-by-Step Solution

1
Identify the vault type required for Azure Virtual Machine backups.
Azure VMs must be backed up to a Recovery Services vault, not a Backup vault.
Azure Backup uses Recovery Services vaults for VM backups, whereas Backup vaults are used for operational backups of other resource types.
2
Determine the storage redundancy type needed to protect against regional disasters.
Configure the vault with Geo-Redundant Storage (GRS).
GRS replicates backup data to a secondary paired region, ensuring availability during a regional disaster.
3
Analyze the policy type needed to support a 1414-day instant restore requirement.
Select an Enhanced backup policy and set instant restore retention to 1414 days.
Standard backup policies only support a maximum of 55 days for instant restore snapshot retention, while Enhanced backup policies support up to 3030 days.

Key Concept

Azure VM backup policy configuration, vault selection, and storage redundancy options.
Estimated Time:2m 0s
Question 16Question →

You are designing a backup solution for Azure Virtual Machines that host a critical business application. The design must meet the following requirements:
- Backups must be recoverable even if the primary Azure region experiences a complete disaster.
- Recent backups from the last 5 days must be available for fast recovery directly from local snapshots without vault latency.
- Backups must be retained for a total of 5 years to meet regulatory compliance.

Which two configurations should you include in the backup design? Select two.

Select all that apply

Show answer & explanation

Answer: A Recovery Services vault configured with Geo-Redundant Storage (GRS); A backup policy with instant restore retention set to 5 days and vault retention set to 5 years

Answer

To meet the requirements, the design must include a Recovery Services vault configured with Geo-Redundant Storage (GRS) and a backup policy with instant restore retention set to 5 days and vault retention set to 5 years.
The correct configurations involve using a Recovery Services vault with Geo-Redundant Storage (GRS) and setting up a backup policy with a 5-day instant restore retention alongside a 5-year vault retention. GRS replicates data to a secondary region to survive regional disasters. Instant restore keeps snapshots locally for quick recovery, but since it is limited to a maximum of 5 days, the remaining 5 years of retention must be kept in the vault standard tier.

Step-by-Step Solution

1
Select the appropriate vault storage redundancy to meet the disaster recovery requirement.
Choose Geo-Redundant Storage (GRS) to replicate backups to a secondary region.
Locally Redundant Storage (LRS) only protects against failures within a single datacenter, whereas GRS protects against a complete regional disaster.
2
Determine the retention settings for fast recovery and compliance.
Configure instant restore retention to 5 days, and vault-tier retention to 5 years.
Instant restore keeps snapshots local for fast restore up to 5 days, but long-term compliance retention (5 years) must be offloaded to the vault tier because instant restore cannot exceed 5 days.

Key Concept

Designing Azure Backup solutions with appropriate vault redundancy and policy retention configuration.
Question 17Question →

An organization is designing a high availability and disaster recovery (HA/DR) solution for a retail application database layer that is migrating to Azure. The database workload depends on SQL Server Agent for scheduled data-aggregation tasks and requires cross-database queries. The solution must meet the following requirements:
- Recover from a regional outage automatically with a Recovery Time Objective (RTO) of less than 1 hour.
- Maintain a single connection string for the application tier that does not require modification during a regional failover.
- Allow read-heavy reporting applications to query the secondary replica in the secondary region to reduce query impact on the primary database.

Which two options should you recommend to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy the databases to Azure SQL Managed Instance.; Create a Failover Group between the primary and secondary Azure SQL Managed Instances, and configure the reporting application to use the read-only listener endpoint.

Answer

Deploy the databases to Azure SQL Managed Instance, and create a Failover Group between the primary and secondary Azure SQL Managed Instances, configuring the reporting application to use the read-only listener endpoint.
The correct design employs Azure SQL Managed Instance because the application relies on SQL Server Agent and cross-database queries, which are not natively supported by Azure SQL Database. To automate failover and prevent client-side configuration changes, a Failover Group must be used. The Failover Group includes a read-write listener that stays active during failover, and a read-only listener that routes reporting traffic to the secondary instance in the disaster recovery region.

Step-by-Step Solution

1
Analyze the application's database compatibility requirements.
Identify that SQL Server Agent and cross-database queries are required. This rules out Azure SQL Database Single Database and Elastic Pools, pointing to Azure SQL Managed Instance as the correct platform.
Choosing the correct deployment option ensures legacy application features work without rewrite overhead.
2
Evaluate the disaster recovery failover automation and endpoint requirements.
Determine that a Failover Group is required because it supports automatic failover and provides a DNS listener endpoint to avoid application connection string changes.
Active Geo-Replication only supports manual failover and lacks unified listener endpoints for failovers.
3
Address the read-scale offloading requirements for reporting workloads.
Point the reporting application to the read-only listener of the Failover Group to target the secondary replica in the failover region.
Using the read-only listener endpoint guarantees that reporting queries are routed to the secondary replica, reducing the workload on the primary instance.

Key Concept

Designing relational database high availability and disaster recovery in Azure requires aligning database engine compatibility with replication capabilities such as Failover Groups.
Question 18Question →

You are designing a backup solution for a production SAP HANA database running on an Azure virtual machine. The solution must satisfy the following requirements:
- Retain weekly full backups for 365 days.
- Ensure backup data is resilient to a primary region outage.
- Enable database restoration to a secondary paired region with minimal delay in the event of a primary region disaster.

Which backup configuration should you recommend?

Show answer & explanation

Answer: A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled.

Answer

A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled.
The correct configuration leverages a Recovery Services vault, which is the required vault type for SAP HANA on Azure VMs. Using Geo-Redundant Storage (GRS) with Cross-Region Restore (CRR) enabled ensures the backups are replicated to the secondary paired region and can be restored there even if the primary region experiences a complete outage.

Step-by-Step Solution

1
Determine the required vault type for the workload.
SAP HANA databases running on Azure VMs must be backed up using a Recovery Services vault rather than a Backup vault.
Azure Backup categorizes workloads; databases on virtual machines are supported under Recovery Services vaults.
2
Select the appropriate storage redundancy and recovery configuration to survive a regional outage.
Configure the vault storage with Geo-Redundant Storage (GRS) and enable Cross-Region Restore (CRR).
GRS replicates data to a paired region, and CRR allows you to restore backup data in the secondary region even when the primary region is healthy or degraded.
3
Configure the backup retention policy parameters.
Set the vault-tier retention to 365 days and ensure the local instant restore snapshot retention is kept within the default limit (1-5 days).
Long-term retention must be configured on the vault tier, as instant restore snapshots cannot exceed the maximum supported limits (up to 30 days for enhanced policies).

Key Concept

Selecting the correct vault type and replication architecture to support disaster recovery for database workloads on Azure VMs.
Estimated Time:1m 30s
Question 19Question →

You are designing a disaster recovery solution for an application that uses an Azure SQL Database. The solution must support automatic failover to a secondary Azure region in the event of a primary region outage. The application must be able to reconnect to the database after failover without any changes to its connection string. Which solution should you recommend?

Show answer & explanation

Answer: Azure SQL Database Failover Groups

Answer

Azure SQL Database Failover Groups
The correct option is Azure SQL Database Failover Groups because they enable automatic failover of a group of databases to a secondary region and provide a listener endpoint. This allows the application to connect using the same connection string regardless of which region is hosting the primary database.

Step-by-Step Solution

1
Analyze the automatic failover requirement.
The database must support automatic failover to a secondary region during a regional outage.
This rules out solutions requiring manual failover or those limited to a single region.
2
Analyze the connection string requirement.
The application must connect using a single, unchanging connection string.
This requires a listener endpoint that redirects traffic automatically, which is a feature of failover groups.

Key Concept

Azure SQL Database Failover Groups provide a read-write listener endpoint that remains constant, automatically routing application traffic to the active primary database in the event of a failover to the secondary region.
Estimated Time:1m 0s
Question 20Question →

A healthcare provider requires a business continuity strategy for an electronic health record (EHR) database migrating to Azure. The database workload has the following requirements:

* It must support legacy cross-database queries and execute SQL Server Agent jobs for nightly aggregation tasks.
* It must survive a regional outage with a Recovery Time Objective (RTO) of 11 hour and a Recovery Point Objective (RPO) of 55 seconds.
* Failover to the secondary region (West US) must occur automatically, using a single connection endpoint that redirects write traffic without requiring application configuration updates.
* Read-only analytical queries must be offloaded to the secondary region.

You plan to implement Azure SQL Managed Instances in East US (primary) and West US (secondary).

Which of the following configuration actions must you perform to satisfy these requirements? (Select 22.)

Select all that apply

Show answer & explanation

Answer: Establish virtual network peering or a VPN connection between the virtual networks of the primary and secondary instances, and configure a failover group.; Manually recreate and synchronize the required SQL Server Agent jobs on the secondary instance.

Answer

To meet the requirements, you must establish network connectivity (VNet peering or VPN) between the virtual networks of the primary and secondary instances to configure a failover group, and manually recreate and synchronize the SQL Server Agent jobs on the secondary instance.
Establishing virtual network connectivity via peering or VPN is a mandatory prerequisite for setting up a failover group between two Azure SQL Managed Instances. The failover group provides automatic failover and a read-write listener that redirects traffic without connection string changes. Because system databases (including msdb) are not replicated by the failover group, SQL Server Agent jobs must be manually recreated on the secondary instance to ensure they run after a failover.

Step-by-Step Solution

1
Determine the relational database deployment tier based on legacy requirements.
Select Azure SQL Managed Instance.
The database requires cross-database queries and SQL Server Agent jobs, which are supported in Managed Instance but not in standard Azure SQL Database offerings.
2
Design the network connectivity required for database replication.
Plan virtual network peering or a VPN connection between the virtual networks in East US and West US.
Failover groups for Azure SQL Managed Instance require bidirectional network communication between the instances.
3
Design the cross-region database failover mechanism.
Configure a failover group containing the user databases.
Failover groups provide automatic failover, meet the RTO/RPO limits, and expose a single read-write listener endpoint to abstract connection changes.
4
Design the synchronization plan for scheduled operations.
Deploy identical SQL Server Agent jobs on the secondary instance.
System databases like msdb are not replicated by the failover group, meaning agent jobs must be manually maintained on the secondary server to run after failover.

Key Concept

Azure SQL Managed Instance HA/DR design using failover groups, virtual network requirements, and handling non-replicated system metadata like SQL Server Agent jobs.
Page 1 / 10Next