Suggested Answer:D🗳️
Before you upload a Windows virtual machine (VM) from on-premises to Azure, you must prepare the virtual hard disk (VHD or VHDX). Scenario: WebApp1 has a web tier that uses Microsoft Internet Information Services (IIS) and a database tier that runs Microsoft SQL Server 2016. The web tier and the database tier are deployed to virtual machines that run on Hyper-V. Reference: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/prepare-for-upload-vhd-image
Answer C: "Use SQL Server transactional replication."
Requirement:
"To avoid disrupting customer access, database downtime must be minimized when databases are migrated."
Transactional replication to Azure SQL Database is now generally available:
We are excited to announce that transactional replication to Azure SQL Database is now generally available (GA).
This feature allows you to migrate your on-premises SQL Server databases to Azure SQL Databases with minimal downtime.
https://azure.microsoft.com/de-de/blog/transactional-replication-to-azure-sql-database-is-now-generally-available
https://devjef.wordpress.com/2016/12/08/setting-up-replication-from-on-premise-sql-server-to-azure-sql-db/
Azure SQL and MS SQL are NOT fully compatible. You can't, if not stated openly, assume that it will work by a chance. It is not stated here that the MS SQL based solution can be or should be (after refactoring) moved to Azure SQL. Hence whole thinking to move into Azure SQL is futile....
The Answer is A. - It is the only answer that meets the criteria and can be implemented with the information given in the scenario.
B & D are no good as they do not meet the criteria "To avoid disrupting customer access, database downtime must be minimized when databases are migrated."
C is no good. No where does it say they have VPN or expressroute to achieve this. Alos they are are not using Azure SQL this is all VMs.
Azure Site Recovery is clearly NOT recommended for migration scenarios, so it would probably not be a featured solution here.
The "solution" should be moved "to Azure," whatever that means. We don't know if they have a VPN connection or not, but the question is what to INCLUDE in the solution. So we can use Transactional Replication. If they don't have ExpressRoute or VPN, we just include that in the solution, too.
Agree with this, the logical answer would be DMS but since this is not an option. Transactional replication is listed as a migration option for SQL in the documentation so makes the most sense:
https://docs.microsoft.com/en-us/azure/azure-sql/migration-guides/database/sql-server-to-sql-database-overview#migration-tools
Site Recovery may work but then you will end up with an IAAS solution which is not ideal. It's always better to go PAAS when possible.
Answer C: "Use SQL Server transactional replication."
Requirement:
"To avoid disrupting customer access, database downtime must be minimized when databases are migrated."
Transactional replication to Azure SQL Database is now generally available:
We are excited to announce that transactional replication to Azure SQL Database is now generally available (GA).
This feature allows you to migrate your on-premises SQL Server databases to Azure SQL Databases with minimal downtime.
https://azure.microsoft.com/de-de/blog/transactional-replication-to-azure-sql-database-is-now-generally-available
https://devjef.wordpress.com/2016/12/08/setting-up-replication-from-on-premise-sql-server-to-azure-sql-db/
c
i think D, as minimal dowbtime accepted. Migrating from on-prem to Azure can use existing licence which will reduce cost.
https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/migrate-to-vm-from-sql-server
https://docs.microsoft.com/en-us/azure/azure-sql/database/migrate-to-database-from-sql-server
"There are two primary methods for migrating a SQL Server 2005 or later database to Azure SQL Database. The first method is simpler but requires some, possibly substantial, downtime during the migration. The second method is more complex, but substantially eliminates downtime during the migration."
Method 2: Use Transactional Replication
C is the answer
ref:
https://docs.microsoft.com/en-us/azure/azure-sql/database/migrate-to-database-from-sql-server
Azure Migrate and Transactional Replication are two primary methods for migrating a SQL Server 2005 or later database to Azure SQL Database.
Azure Migrate is simpler but requires some, possibly substantial, downtime during the migration.
Azure Site Recovery is same as Azure Migrate. I've been using ASR and Azure Migrate for years, and worked with Azure project teams. At backend, they use almost same approach and technology. If you check price of them, pricing are exactly same.
When you can't afford to remove your SQL Server database from production while the migration is occurring, you can use SQL Server transactional replication as your migration solution. So C is correct.
MS actually has a very good website to help with the migration
https://docs.microsoft.com/en-us/data-migration/
Select "SQL Server" to the taget, for example, azure sql database
, then you will go to https://docs.microsoft.com/en-us/azure/azure-sql/migration-guides/database/sql-server-to-sql-database-overview
From there, there are recommended solutions and "C" is correct.
but how do you get the database to azure to begin with? transactional replication alone doesn't migrate it. ASR allows the whole database and low RTO. it can cutover in a matter of a couple minutes.
Option D sounds correct as per this article - https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/migrate-to-vm-from-sql-server
"Convert on-premises machine to Hyper-V VHDs, upload to Azure Blob storage, and then deploy a new virtual machine using uploaded VHD"
Use when bringing your own SQL Server license, when migrating a database that you'll run on an older version of SQL Server, or when migrating system and user databases together as part of the migration of database dependent on other user databases and/or system databases.
Correct answer A: Use Azure Site Recovery to replicate the SQL servers to Azure
You need to migrate all server ( WebApp1 + database ) to azure virtual machine so Use Azure Site Recovery to replicate the SQL servers to Azure.
https://docs.microsoft.com/en-us/azure/migrate/tutorial-migrate-hyper-v?tabs=UI
This links actually tells you NOT to use Azure Site Recovery but Azure Migrate (which uses some components from Site Recovery but is still something different).
"Site Recovery should be used for disaster recovery only, and not migration."
https://docs.microsoft.com/en-us/azure/site-recovery/migrate-tutorial-on-premises-azure
Option C required SQL Server to be compatible with Azure SQL Database.
https://docs.microsoft.com/en-us/azure/azure-sql/database/replication-to-sql-database
In my opinion too many changes are requred.
Options B, D want to move Azure SQL Database files but SQL Server files are not the same
My opinion after reading the suggestions here, the question requirements and researching some documentation:
"When you can't afford to remove your SQL Server database from production while the migration is occurring, you can use SQL Server transactional replication as your migration solution"
From <https://docs.microsoft.com/en-us/azure/azure-sql/database/migrate-to-database-from-sql-server#method-2-use-transactional-replication>
This section is not available anymore. Please use the main Exam Page.AZ-304 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Stephan99
Highly Voted 4 years, 1 month agoTKCZ
3 years, 11 months agoUnknownSecret
3 years, 8 months agoUnknownSecret
3 years, 8 months agoMoley
Highly Voted 3 years, 11 months agopentium75
3 years, 8 months agoBoxGhost
3 years, 7 months agoxyz213
Most Recent 3 years, 3 months ago[Removed]
3 years, 3 months agoDpejic
3 years, 4 months agochichi0307
3 years, 6 months agosyu31svc
3 years, 7 months agoAD3
3 years, 1 month agoleo_az300
3 years, 7 months agopoplovic
3 years, 7 months agojamess
3 years, 8 months agoSPJunk
3 years, 8 months agopentium75
3 years, 8 months agohoangton
3 years, 9 months agopentium75
3 years, 8 months agonorbitek
3 years, 10 months agoSriRamOne
3 years, 11 months agoSriRamOne
3 years, 11 months agonabylion
3 years, 11 months agoPandaTuga
3 years, 11 months agoAWS56
4 years ago