Exam AZ-305 All Questions

View all questions & answers for the AZ-305 exam

Exam AZ-305 topic 3 question 18 discussion

Actual exam question from Microsoft's AZ-305

Question #: 18
Topic #: 3

HOTSPOT
-

You have two on-premises Microsoft SQL Server 2017 instances that host an Always On availability group named AG1. AG1 contains a single database named DB1.

You have an Azure subscription that contains a virtual machine named VM1. VM1 runs Linux and contains a SQL Server 2019 instance.

You need to migrate DB1 to VM1. The solution must minimize downtime on DB1.

What should you do? 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, 7:10 p.m.

Comments

Submit Cancel

RajFamily25

Highly Voted 2 years, 7 months ago

First one should be A: Prepare For the migration by: A. Adding a secondary replica to AG1 Reason: Creating an Always On availability group on VM1 would not be necessary, as you already have an availability group (AG1) in place on your on-premises SQL Server instances. By adding a secondary replica to AG1, you can provide a copy of DB1 that can be used for the migration. This will allow you to minimize downtime on DB1 by performing the migration on the secondary replica, while the primary replica remains available for use. Perform the migration by using: B. Azure migrate

upvoted 54 times

betterthanlife

2 years, 3 months ago

Please, stop voting this guy up, he's not thinking, he's just copy/pasting the explanation from another exam dump. In this case it is correct that option A is "Adding a secondary replica to AG1"... I know this because I researched it. But other questions that he posts (plagiarizes) in are WRONG responses.

upvoted 68 times

betterthanlife

2 years, 3 months ago

This article clearly covers adding a Linux SQL server to an existing AonAG. https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-availability-group-cross-platform?view=sql-server-ver16 Furthermore, Azure Migrate does not allow targeting a Linux box in Azure IaaS, it only allows targeting Azure SQL or Azure Managed Instance. https://www.youtube.com/watch?v=QNmkaWi3Ltk Correct responses: Adding a secondary replica to AG1 Log shipping

upvoted 13 times

betterthanlife

2 years, 3 months ago

I was incorrect in my above response for option 2, how to migrate (Log shipping IS NOT correct) as when I was looking in the portal I only saw Azure SQL DB & MI. This video clearly shows at 11:35 you can migrate to an Azure IaaS VM running SQL (evidentially one that is running Linux) - Adding a secondary replica to AG1 - Azure Migrate

upvoted 28 times

theboywonder

2 years, 1 month ago

ofc it's running "SQL server" on linux

upvoted 2 times

...

Load full discussion...

...

curtmcgirt

2 years, 4 months ago

does it matter that vm1 "runs linux and sql server 2019" but on-prem AG1 sql is 2017?

upvoted 3 times

willybsmith

2 years, 2 months ago

Yep..one of the Microsoft pages notes "Only replicas that are on the same major build of SQL Server will be readable. See Rolling upgrade basics for more information." so maybe its update the older on prem version first?

upvoted 2 times

...

RandomNickname

2 years, 7 months ago

Absolutely agree.

upvoted 3 times

RandomNickname

2 years, 7 months ago

To confirm it should be; Secondary replica Azure Migrate The given answer by exam topics is wrong.

upvoted 7 times

...

chessace2000

Highly Voted 2 years, 6 months ago

This should be 1. Creating an Always On availability group on VM1 2. Use distributed availablity group Reference: https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-distributed-availability-group-migrate-ag?view=azuresql

upvoted 46 times

DeBoer

2 years, 5 months ago

the link you provided, together with the prereqs in https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-distributed-availability-group-migrate-prerequisites?view=azuresql , show that this makes the most sense. Same version of SQL is recommended - but not required in this scenario.

upvoted 4 times

...

steel72

2 years, 4 months ago

I think this is wrong, in the link you provide it states that Windows Server Failover Cluster is required. The target machine runs Linux.

upvoted 4 times

...

fishy_resolver

2 years, 3 months ago

The question seems to hint towards using distributed availability groups to do the migration. But for 1. I would rather say the secondary replica. There is already an availability group AG1 on VM1. And the steps in the link you provided requires you to add a target availability group.

upvoted 1 times

...

wooyourdaddy

1 year, 10 months ago

This link also shows mixed OS Availability Groups and Distributed Availability Groups: https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-availability-group-overview?view=sql-server-ver16#interoperability-with-windows-based-availability-groups-and-replicas

upvoted 2 times

...

hwoccurrence

Most Recent 3 months, 1 week ago

Preparation: Creating an Always On availability group on VM1 is necessary to establish the target environment. A distributed availability group (DAG) requires both the source (on-premises AG1) and target (VM1) to have their own availability groups. This setup bridges the two environments, enabling cross-platform (Windows → Linux) and cross-version (SQL 2017 → 2019) replication. Migration Method: Distributed availability group (DAG) is explicitly designed for minimal downtime migrations. It allows asynchronous replication between the on-premises AG1 and the new AG on VM1, followed by a controlled failover. This aligns with Microsoft’s recommended approach for migrating Always On availability groups to Azure VMs, especially in heterogeneous environments.

upvoted 3 times

...

Rwj

4 months ago

WHERE IS MALTONIS?????

upvoted 1 times

...

Muler5692

4 months, 3 weeks ago

- Adding a secondary replica to AG1 - Azure Migrate

upvoted 1 times

...

424ede1

4 months, 3 weeks ago

1. Creating an Always On availability group on VM1 2. Use distributed availability group Choose method from first link and prerequisites from the second! https://learn.microsoft.com/en-us/data-migration/sql-server/virtual-machines/overview https://learn.microsoft.com/en-us/data-migration/sql-server/virtual-machines/distributed-availability-group-prerequisites

upvoted 1 times

424ede1

4 months, 3 weeks ago

https://learn.microsoft.com/en-us/data-migration/sql-server/virtual-machines/overview#migrate DAG minimizes downtime. Use when you have an availability group configured on-premises.

upvoted 1 times

...

ishqms24

9 months ago

This question is still relavent (10 Nov 2024) , but I was not sure about answers as so many options are discussed. I choose 1. Replica AG1 2. Azure Migrate

upvoted 1 times

...

Teerawee

11 months ago

•Prepare for the migration by: Adding a secondary replica to AG1 •Perform the migration by using: A distributed availability group

upvoted 5 times

...

23169fd

1 year, 1 month ago

The correct answer should be : Adding a secondary replica to AG1: Ensures continuous data synchronization between the on-premises environment and VM1 during the migration, minimizing downtime. Using a distributed availability group: Provides a seamless and robust mechanism for high availability, real-time data replication, and automatic failover capabilities, ensuring minimal downtime during the migration process.

upvoted 5 times

...

profesorklaus

1 year, 3 months ago

I see some of the answers and I dont understand some: how can you create Creating an Always On availability group on VM1 if you have only one virtual machine with one SQL server? The idea of creating Always On Availability Group is to involve two servers. You can't do it with one server but even if you could it wouldn't make any sense. To do this migration I believe you need to uprade sql servers on prem and use Azure Database MIgration Service. Adding a secondary replica is technically feasible but if you do it then database will be replicated automatically (synchronously or asynchronously). What is the reason to use Azure migrate then? My option is * upgrade on prem servers * use Azure Mgrate (Azure Database MIgration Service to be more precise)

upvoted 2 times

profesorklaus

1 year, 3 months ago

Azure MIgration is dedicated if downtime must be zero. You can still use primary db when migrating db. Additionaly this task refers to one-time migration which need to be done ONCE.

upvoted 1 times

...

jayaj

1 year, 3 months ago

If you extend the existing on-prem AG to AZURE by adding another replica, why do you need to migrate DB, isn't the SQL synchronization copy the DB to new replica? Considering the given options, I think only possible selection here is Creating an Always On availability group on VM1 and using a distributed AG. Also AZURE migrate is not for DB migrations and it's for recommendation and advise about migration, isn't it?

upvoted 2 times

ValB

10 months, 2 weeks ago

Fromnthe documentation it seems that it is also for migration, not just for preparation.

upvoted 1 times

...

Lazylinux

1 year, 4 months ago

I would go for 1. Creating an Always On availability group on VM1 2. Use distributed availability group that can be configured to include both Availability groups AG1 and the new one in Azure on Linux VM, thank you can perform the failover from there Read this carefully https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/distributed-availability-groups?view=sql-server-ver15

upvoted 7 times

...

177c705

1 year, 5 months ago

box1 : Creating an Always On availability group on VM1 box2: Use Distributed availability group

upvoted 5 times

...

TonySuccess

1 year, 6 months ago

Surely for question 1 you would add a Secondary Replica to an already existing Availability Group?

upvoted 1 times

...

MiniLa92

1 year, 6 months ago

Got this ques in my exam on 29th Jan 2024 and scored 950. I chose box1 : Creating an Always On availability group on VM1 box2: Use Distributed availability group

upvoted 12 times

...

nchebbi

1 year, 8 months ago

I think the answer should be either: B & A: creating an always On availibility group on VM1 and use a distributed availibility group. OR C & B: Upgrade the On premesises SQL server & Use Azure Migrate. Those are the only valid options. Log shipping only supports Windows (ref1), From ref2: Azure Migrate only supports LIFT& SHIT it doesn't support upgrading versions "SQL server is to be moved as-is" (though C&B, but there will be a down time). Using Distibuted AG it's recommended to have same versions BUT you can use it to migrate to a higher version and SEED the data Manually (again down time). I'm leaning more toawd B&A.

upvoted 1 times

nchebbi

1 year, 8 months ago

ref1: https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-to-sql-on-azure-vm-migration-overview?view=azuresql#lift-and-shift:~:text=to%20Blob%20storage-,Log%20shipping,SQL%20Server%202012%20SP4%20(Windows%20Only),-Azure%20VM%20storage ref2:https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-to-sql-on-azure-vm-migration-overview?view=azuresql#lift-and-shift

upvoted 1 times

...

nchebbi

1 year, 8 months ago

ref3: about distibuted AG :"If you choose to upgrade during the migration process by using a higher version of SQL Server on the target, then you will need to manually seed your database rather than relying on autoseeding as is provided in this series of articles." https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-distributed-availability-group-migrate-prerequisites?view=azuresql

upvoted 1 times

...

mmarkiew

1 year, 8 months ago

I believe the answers are: Creating an Always On availability group on VM1 A distributed availability group If you review the following article, you'll see that Azure Migrate is used for lift-and-shift scenarios and moves SQL Server instances as-is to the target VMs without changes to the SQL Server version (which is required in this case). https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-to-sql-on-azure-vm-migration-overview?view=azuresql-vm In that same article, you'll see that distributed availability groups are recommended for migration scenarios where you need to minimize downtime and already have an availability group configured on-premises.

upvoted 2 times

mmarkiew

1 year, 8 months ago

Part of the process of configuring a distributed availability group involves setting up an availability group on the target SQL Server VMs, as explained in the following article (under "Create target AG"): https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-distributed-availability-group-migrate-ag?view=azuresql Although it's recommended to use the same source and target versions of SQL Server for the migration, it's possible to migrate to a later version. This requires manually seeding the target DBs, but that shouldn't result in any downtime: https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/distributed-availability-groups?view=sql-server-ver16#migrate-to-higher-sql-server-versions

upvoted 2 times

...

Load full discussion...