Exam AZ-305 All Questions

View all questions & answers for the AZ-305 exam

Exam AZ-305 topic 3 question 17 discussion

Actual exam question from Microsoft's AZ-305

Question #: 17
Topic #: 3

HOTSPOT
-

You have an on-premises Microsoft SQL Server database named SQL1.

You plan to migrate SQL1 to Azure.

You need to recommend a hosting solution for SQL1. The solution must meet the following requirements:

• Support the deployment of multiple secondary, read-only replicas.
• Support automatic replication between primary and secondary replicas.
• Support failover between primary and secondary replicas within a 15-minute recovery time objective (RTO).

What should you include in the solution? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Show Suggested Answer

Suggested Answer:

by maku067 at Jan. 5, 2023, 5:49 p.m.

Comments

Submit Cancel

zellck

Highly Voted 2 years, 5 months ago

1. Azure SQL DB 2. Active geo-replication https://learn.microsoft.com/en-us/azure/azure-sql/database/features-comparison?view=azuresql#resource-limits Azure SQL Database -Read-only replicas Read scale with 1-4 high availability replicas or 1-30 named replicas 0 - 4 geo-replicas

upvoted 72 times

yonie

2 years, 3 months ago

This seems to be a tricky question: Since choosing Azure SQL DB includes the General Purpose tier that doesnt have replicas, I would argue that we need to choose Hyperscale as the best answer. Under Azure SQL DB we have three service tiers: General Purpose, Business Critical and Hyperscale. *Business Critical* supports up to 3 replicas: "Every database is a cluster of database nodes with one primary replica that is accessible for customer workloads, and three secondary replicas containing copies of data. " https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tiers-sql-database-vcore?view=azuresql#business-critical Hyperscale supports up to 4 replicas https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tiers-sql-database-vcore?view=azuresql#hyperscale

upvoted 9 times

c_h_r_i_s_

9 months, 4 weeks ago

"Support the deployment of multiple secondary, read-only replicas." - only hyperscale can do that.

upvoted 1 times

...

bluedave

2 years ago

I think this a good point. Despite the article that zellck points out, GP uses shared premium storage for DR, not replicas.

upvoted 1 times

...

mtc9

1 year, 6 months ago

I'm pretty sure that BC supports 1 replica

upvoted 2 times

...

zellck

2 years, 5 months ago

https://learn.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-overview?view=azuresql Active geo-replication is a feature that lets you create a continuously synchronized readable secondary database for a primary database. The readable secondary database may be in the same Azure region as the primary, or, more commonly, in a different region. This kind of readable secondary database is also known as a geo-secondary or geo-replica. Active geo-replication is designed as a business continuity solution that lets you perform quick disaster recovery of individual databases in case of a regional disaster or a large scale outage. Once geo-replication is set up, you can initiate a geo-failover to a geo-secondary in a different Azure region. The geo-failover is initiated programmatically by the application or manually by the user.

upvoted 2 times

...

zellck

2 years, 5 months ago

To support 15 mins RTO, only manual failover can meet the requirements. https://learn.microsoft.com/en-us/azure/azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview?view=azuresql#recover-a-database-to-the-existing-server Manual database failover refers to failover of a single database to its geo-replicated secondary using the unplanned mode. See the table earlier in this article for details of the auto-failover RTO and RPO. Manual database failover - RTO - 30s https://learn.microsoft.com/en-us/azure/azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview?view=azuresql#recover-a-database-to-the-existing-server

upvoted 4 times

...

zellck

2 years, 5 months ago

https://learn.microsoft.com/en-us/azure/azure-sql/database/features-comparison?view=azuresql#platform-capabilities Azure SQL Database Active geo-replication - Yes - all service tiers.

upvoted 8 times

...

Load full discussion...

...

NotMeAnyWay

Highly Voted 2 years, 4 months ago

1. Azure service or service tier? c. The Hyperscale service tier (of Azure SQL Database) The Hyperscale service tier supports the deployment of multiple secondary, read-only replicas, automatic replication between primary and secondary replicas, and failover capabilities. It also allows you to scale out the read workload, which meets the requirements mentioned in the question. 2, Replication mechanism? a. Active geo-replication Active geo-replication supports the creation of up to four readable secondary replicas within the same or different Azure regions. It provides automatic replication between primary and secondary replicas, and you can initiate failover manually when needed. The recovery time objective (RTO) for active geo-replication is less than 30 seconds, which meets the requirement of a 15-minute RTO.

upvoted 10 times

...

Thameur01

Most Recent 1 month ago

Azure SQL Database Hyperscale • Offers high scalability but does not support zone redundancy yet. • Failover might result in data loss (due to asynchronous replication). • Not the best choice for zone outage or data-loss prevention.

upvoted 1 times

...

Thameur01

1 month ago

1. Azure SQL DB 2. Active geo-replication

upvoted 1 times

...

ShanYuen

1 month, 2 weeks ago

I'm sure everyone here didn't read the question carefully or dont have experience migrating a database from on-premise to Azure. The question not just about high availability, but compatibility to migrate onpremise sql server to Azure. On-premise SQL is best moved to a Managed Instance, without having to change DB structure and removing functions that only exist in on-premise. MI and Auto-failover groups also meets all the requirements.

upvoted 1 times

...

hwoccurrence

3 months, 1 week ago

Correct: Hyperscale Service Tier: Supports multiple secondary, read-only replicas (up to 30 named replicas). Designed for high scalability and read-heavy workloads. Active Geo-Replication: Enables automatic replication between primary and secondary replicas. Supports up to four geo-replicas, meeting the requirement for multiple secondary replicas. Allows manual failover with RTO <30 seconds, well within the 15-minute requirement.

upvoted 2 times

...

d717098

3 months, 3 weeks ago

As others have commented, the question says nothing about regional failover, so why are ALL options in replication box for geo- replication? This question seems to be designed to sow confusion about Microsoft's own products. Hyperscale is only needed for regional failover, otherwise Premium or business critical provide multiple secondary replicas. https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla-local-zone-redundancy?view=azuresql&tabs=azure-powershell#premium-and-business-critical-service-tier-zone-redundant-availability

upvoted 1 times

...

Y2

4 months, 1 week ago

Answer - HyperScale service tier & Active Geo-Replication. (MI & vCore) Business critical + Geo-Replication only supports 1 read-only secondary. https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tiers-sql-database-vcore?view=azuresql https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/service-tiers-managed-instance-vcore?view=azuresql&tabs=azure-portal Auto-Failover only provides one read-only secondary rep https://learn.microsoft.com/en-us/azure/azure-sql/database/failover-group-sql-db?view=azuresql

upvoted 1 times

...

Thanveer

9 months ago

* Multiple replicas, up to four read scale-out, zone-redundant HA * A choice of locally redundant (LRS), zone-redundant (ZRS), or geo-redundant (GRS) storage 1-35 days (seven days by default) retention, with up to 10 years of long-term retention available

upvoted 1 times

Thanveer

9 months ago

Given Answers are correct. Explanation is above

upvoted 1 times

...

3c5adce

9 months, 1 week ago

Azure service or service tier: Azure SQL managed Instance This option supports high availability and automatic failover with multiple secondary, read-only replicas, making it suitable for enterprise applications needing high availability. Replication mechanism: Auto-failover groups Auto-failover groups enable automated failover for databases across Azure regions with a low recovery time, meeting the 15-minute RTO requirement.

upvoted 1 times

...

Teerawee

10 months, 3 weeks ago

Azure SQL Managed Instance Auto-failover groups

upvoted 1 times

...

RJ06

11 months, 3 weeks ago

I think its Azure SQL DB and Active-Geo Replication The article below suggests that with correct BCP plan, Azure SQL DB with active geo failover can provide rto of less than 60 secs. Hence third scenario is also supported. The only confusing bit is the first requirement, i.e. whether they are talking about multiple read replicas within the service tier itself in which case Hyperscale will be the only option. refer to https://learn.microsoft.com/en-us/azure/azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview?view=azuresql-db&preserve-view=true#rto-and-rpo

upvoted 3 times

...

23169fd

1 year, 1 month ago

Given the requirements: Support the deployment of multiple secondary, read-only replicas. Support automatic replication between primary and secondary replicas. Support failover between primary and secondary replicas within a 15-minute recovery time objective (RTO). The best combination would be: Azure Service or Service Tier: Azure SQL Managed Instance or Azure SQL Database Business Critical (both can meet the high availability and read replica requirements) Replication Mechanism: Auto-failover groups

upvoted 1 times

...

jayaj

1 year, 3 months ago

Zone redundancy and read replicas are 2 different things. Only the Hyperscale has read replicas and general, premium and business critical has zone redundancy, so box 1 should be Hyperscale.

upvoted 2 times

...

Lazylinux

1 year, 4 months ago

I would say box 1 => Hyperscale as multiple read only replica as per below Hyperscale (Highly scalable compute and Storage): The widest variety of workloads, including those workloads with highly scalable storage and read-scale requirements. Offers higher resilience to failures by allowing configuration of more than one high availability secondary replica. The Hyperscale service tier is suitable for all workload types. Its cloud native architecture provides independently scalable compute and storage to support the widest variety of traditional and modern applications. Compute and storage resources in Hyperscale substantially exceed the resources available in the General Purpose and Business Critical tiers Box 2 => Active Geo-Replication

upvoted 2 times

...

rishisoft1

1 year, 4 months ago

In the question, it's asking the service tier and also says multiple replica and read replica both. In option 1, only Hyperscale is the service tier. I am thinking, it should be Hyperscale as 1st option

upvoted 1 times

...

varinder82

1 year, 4 months ago

Final Answer: 1. Hyperscale: For Multiple read only replicas 2.Active geo-replication

upvoted 2 times

...

Load full discussion...