I think A is correct - hybrid benefit is available for vcore-based servers and this would be more cost effective than vm-based - "Azure Hybrid Benefit for SQL Server is available to all vCore-based options: SQL Database Managed Instance, Single Database and Elastic Pool"
The question is for data storage solution not for WebApp1. Below are requirments for WebApp1 database
1. Database metrics for the production instance of WebApp1 must be available for analysis so that database administrators can optimize the performance settings.
2. To avoid disrupting customer access, database downtime must be minimized when databases are migrated.
3. Database backups must be retained for a minimum of seven years to meet compliance requirements.
Batabase backup for minimum 7 years. The better choice is Long-term backup retention (LTR) which leverages the full database backups that are automatically created to enable point in time restore (PITR). LTR only support for Azure SQL Database and Azure SQL Managed Instance. Therefore B is eliminated.
To optimize the performance setting, a fixed-size DTU can not meet tunning requirements. Therfore D is eliminated.
C has nothing to do with above 3 requirements. So I would choose A as the answer
Reviewing the question I think the correct answer is actually C and I'll explain why:
From my point of view here the requirement for a database storage strategy is the following:
"The use of WebApp1 is unpredictable. At peak times, users often report delays. At other times, many resources for WebApp1 are underutilized."
If you go to the official Microsoft documentation on Elastic Pools you will find the following:
"Azure SQL Database elastic pools are a simple, cost-effective solution for managing and scaling multiple databases that have varying and unpredictable usage demands."
To aprofound the topic please refer to the following document:
https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-overview
Elastic Pools only make sense if you have multiple DBs that can share the capcities of the pool they are in.
We only have one DB here. So there's no point in using a pool imho.
not sure we are only talking about 1 DB, as per:
-To avoid disrupting customer access, database downtime must be minimized when databases are migrated.
Since the company already has existing Microsoft licenses with software assurance, they can opt for a hybrid model in which they can benefit from huge discounts.
https://docs.microsoft.com/en-us/azure/azure-sql/azure-hybrid-benefit?tabs=azure-powershell
a strategy will be vCore instead of fixed-size DTU. So (A) is better than (C). In order to achieve the goal (hybrid benefit etc to reduce cost), (C) still needs to use vCore.
Correct answer: B. an Azure virtual machine that runs SQL Server
We need to have: minimal downtime during migration and hybrid benefits. The both are in B.
C - doesn't make any sense (no elastic pool case)
D - doesn't have hybrid benefit.
Why A is incorrect? Because we don't have zero-migration downtime.
The Managed Instance solution will be the best (online migration, easy to manage and hybrid benefit) but we don't have this option
Agree with this thinking. We can't replace a full server with just a database. For transaction log based migration, we can only use SQL MI, or SQL Server VM and we would use the SQL IaaS extension in full managed mode.
Supported configurations
Azure SQL Database can only be the push subscriber of a SQL Server publisher and distributor.
The SQL Server instance acting as publisher and/or distributor can be an instance of SQL Server running on-premises, an Azure SQL Managed Instance, or an instance of SQL Server running on an Azure virtual machine in the cloud.
The distribution database and the replication agents cannot be placed on a database in Azure SQL Database.
Snapshot and one-way transactional replication are supported. Peer-to-peer transactional replication and merge replication are not supported.
Versions
To successfully replicate to a database in Azure SQL Database, SQL Server publishers and distributors must be using (at least) one of the following versions:
Publishing to any Azure SQL Database from a SQL Server database is supported by the following versions of SQL Server:
SQL Server 2016 and greater
SQL Server 2014 RTM CU10 (12.0.4427.24) or SP1 CU3 (12.0.2556.4)
SQL Server 2012 SP2 CU8 (11.0.5634.1) or SP3 (11.0.6020.0)
If someone expects that a DB once runing on Microsoft SQL Server 2016 will run quickly or flawlesly - see: "To avoid disrupting customer access, database downtime must be minimized when databases are migrated." - after migrated to Azure SQL, then: GOOD LUCK! As Azure SQL MAnaged instance areot mentioned, there is nothing to deliberate about. It must go on a VM based SQL to provide 100% compability. If not then refactoring is demanded,refactorig here not mentioned.
Elastic Pool can be based on either DTU or vCore
https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-overview
vCore vs DTU
https://www.youtube.com/watch?v=1AKDj0_wOFs
Therefore, the answer can be Elastic Pool and vCore
Elastic pool is not db equivalent for VM scale set. It is only cost optimize solution in many DBs case. Here we have only 1 db. So elastic pool doesn't have any sens.
C. an Azure SQL Database elastic pool
The elastic pool also has V-Core purchasing model and Hybrid Benefits.
https://azure.microsoft.com/en-au/pricing/details/azure-sql-database/elastic/
The use of WebApp1 is unpredictable. At peak times, users often report delays. At other times, many resources for WebApp1 are underutilized.
Elastic pool is not db equivalent for VM scale set. It is only cost optimize solution in many DBs case. Here we have only 1 db. So elastic pool doesn't have any sens.
It is highly unlikely that a international company this size with offices across Europe service offering would have one database.
"To avoid disrupting customer access, database downtime must be minimized when databases are migrated."
Where does it say there is only one DB? it specifically says downtime must be minimised when the databases are migrated, suggesting there are multiple databases.
"To avoid disrupting customer access, database downtime must be minimized when databases are migrated."
"The use of WebApp1 is unpredictable. At peak times, users often report delays. At other times, many resources for WebApp1 are underutilized." shouldnt be SQL Database elastic pool with V-Core pricing model? A & C combo
Elastic pool is not db equivalent for VM scale set. It is only cost optimize solution in many DBs case. Here we have only 1 db. So elastic pool doesn't have any sens.
I'd choose B
what they have:
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.
Fabrikam purchases all Microsoft licenses through a Microsoft Enterprise Agreement that includes Software Assurance.
from req:
Whenever possible, existing on-premises licenses must be used to reduce cost.
Database metrics for the production instance of WebApp1 must be available for analysis so that database administrators can optimize the performance settings.
To avoid disrupting customer access, database downtime must be minimized when databases are migrated.
suggest hybrid benefit and azure migration
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.
AlanJP
Highly Voted 3 years, 9 months agodennnnnnnnnn
3 years, 8 months agoleo_az300
Highly Voted 3 years, 7 months agordemontis
3 years, 5 months agordemontis
3 years, 4 months agobugimachi
3 years, 4 months agoagente232
3 years, 3 months agoAberdeenAngus
2 years, 9 months agoSnownoodles
Most Recent 2 years, 6 months agoDpejic
3 years, 4 months agoKubernetes
3 years, 4 months agosyu31svc
3 years, 7 months agopoplovic
3 years, 7 months agoaddam23
3 years, 8 months agoyyuryyucicuryyforme
3 years, 3 months agoFinMessner
3 years, 3 months agoFinMessner
3 years, 3 months agoUnknownSecret
3 years, 8 months agojieaws
3 years, 9 months agoaddam23
3 years, 8 months agoBrettusMaximus
3 years, 9 months agoaddam23
3 years, 8 months agostack120566
3 years, 3 months agoBoxGhost
3 years, 8 months agohahmed
3 years, 9 months agoaddam23
3 years, 8 months agonExoR
3 years, 10 months agoSonkuB
3 years, 9 months agoSonkuB
3 years, 9 months ago