Suggested Answer:
Box 1: SQL Managed Instance - Scenario: Once migrated to Azure, DB1 and DB2 must meet the following requirements: ✑ Maintain availability if two availability zones in the local Azure region fail. ✑ Fail over automatically. ✑ Minimize I/O latency. The auto-failover groups feature allows you to manage the replication and failover of a group of databases on a server or all databases in a managed instance to another region. It is a declarative abstraction on top of the existing active geo-replication feature, designed to simplify deployment and management of geo- replicated databases at scale. You can initiate a geo-failover manually or you can delegate it to the Azure service based on a user-defined policy. The latter option allows you to automatically recover multiple related databases in a secondary region after a catastrophic failure or other unplanned event that results in full or partial loss of the SQL Database or SQL Managed Instance availability in the primary region.
Box 2: Business critical - SQL Managed Instance is available in two service tiers: General purpose: Designed for applications with typical performance and I/O latency requirements. Business critical: Designed for applications with low I/O latency requirements and minimal impact of underlying maintenance operations on the workload. Reference: https://docs.microsoft.com/en-us/azure/azure-sql/database/auto-failover-group-overview https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview
Elastic Pool.
Managed instance does not support zone redundancy
Zone-redundant configuration is not available in SQL Managed Instance. In SQL Database this feature is only available when the Gen5 hardware is selected.
https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell
We're talking about 2 DBs, so a single DB won't cut it. Managed Instances support zone redundancy in preview - so that's not something we'd want in production yet. Only option left: elastic pool. Makes sense since we're using 2 DBs.
Regarding the tier:
General Purpose fits the bill for zone redundancy - you can turn on Zone Redundancy in GP. However... they also want high IOPS (requirement 3). So that means Business Critical or Hyperscale (500 IOPS per vCore with 7,000 maximum IOPS in GP, 8,000 IOPS per vCore with 200,000 maximum in BC an Hyperscale has 327,680 IOPS with max local SSD).
I'm not sure if you can use Hyperscale with elastic pools (portal won't let me select it in my lab), so I'd go for Business Critical.
Updating my comment: now the feature is in preview, but for production and reduce administrative effort, i would still go with elastic pool:
https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell
This feature is currently in Preview for SQL Managed Instance. In SQL Database, when using the Business Critical tier, zone-redundant configuration is only available when the standard-series (Gen5) hardware is selected. For up to date information about the regions that support zone-redundant databases, see Services support by region.
CORRECT
WARNING! This is not the same question as Q1 in Topic 12
Topic 12 Qeustion 1:
You PLAN to MIGRATE DB1 and DB2 to Azure.
You need to ensure that the Azure database and the service tier meet the resiliency and business requirements.
An Azure SQL Database elastic pool
Business Critical
Topic 15 Qeustion 1:
How SHOULD the MIGRATED databases DB1 and DB2 be IMPLEMENTED in Azure?
Azure SQL Managed Instance
Business Critical
(MI supports ZR by now)
1.SQL Managed Instance
2. Business Critical service tier
"Zone-redundant configuration is currently in preview for SQL Managed Instance, and only available for the Business Critical service tier."
https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell
Hello guys,
I guess is correct, should be the following:
> Database: "AZURE SQL MANAGED INSTANCE" - it can provide AUTO-FAILOVER
> Service Tier: "Business Critical"
Question #1-Page47 - this question looks similar
for this question the answer is Elastic Pool now Why Single Azure SQL Database here?
I think GarryK is correct
Single Azure SQL Database
Business Critical
Indeed a repeated question IMHO
A single azure sql db for each db would meet the requirements.
You can't use an elastic pool unless you are aware of the load pattern of each db to make it worthwhile to use elastic db. There is no indication in the question to hint pool will be useful.
also there is no indication in the answer that single azure db has to be for both dbs. It can a single db for each - db1 and db2. Therefore Multi DB in question doesn't rule out a single azure db as potential answer.
SQL Managed Instance does support zone redundancy, however you need to choose Gen5 hardware, so it all depends on when this question was released. One of the business requirements is to minimize cost, so elastic pool would be the preferred choice to minimize cost, however MI would work too.
Yes, Azure SQL Managed Instance supports Zone Redundancy. Zone Redundancy is a feature that provides additional resiliency and availability for Azure SQL Managed Instance by replicating the data to a secondary region within the same geography. This allows you to maintain availability in the event of a region-wide failure or disaster.
To enable Zone Redundancy for your Azure SQL Managed Instance, you can specify the zone redundancy option when you create the instance. You can also enable or disable this feature later on by modifying the instance's properties.
It's important to note that Zone Redundancy is only available for Azure SQL Managed Instance in the General Purpose and Business Critical service tiers. It is not available for the Hyperscale service tier.
I think you are getting confused.
"Zone Redundancy is a feature that provides additional resiliency and availability for Azure SQL Managed Instance by replicating the data to a secondary region within the same geography" - Wrong.
See below correction:
Zone Redundancy is a feature that provides additional resiliency and availability for Azure SQL Managed Instance by replicating the data across multiple physical locations within an Azure region.
Note - "Physical Locations"
Meaning, your data is replicated to other availability zones within the same region. Hence "ZONE" Redundancy.
An availability zone consists of one or more data centers (physical locations).
Agree with others.
Elastic Pool
Multi DB so not Azure SQL and as per below not SQL MI either
Business Critical
https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell
From above URL;
Premium and Business Critical service tier zone redundant availability
This feature is not available in SQL Managed Instance. In SQL Database, when using the Business Critical tier, zone-redundant configuration is only available when the standard-series (Gen5) hardware is selected. For up to date information about the regions that support zone-redundant databases, see Services support by region.
Correction.
After a further look given answer looks correct.
SQL MI does support zone redundancy.
https://techcommunity.microsoft.com/t5/azure-sql-blog/zone-redundancy-for-azure-sql-managed-instance-business-critical/ba-p/3677646
According to official docs https://learn.microsoft.com/en-us/azure/azure-sql/database/features-comparison?view=azuresql#platform-capabilities it is still in Preview. This means it is not official for the general public. Also I doubt that the test questions are updated on monthly basis for the latest feature updates. Not sure though, question is a bit tricky.
Great point regarding preview mode, and the frequency of when the questions are updated.
There are usually assumptions with Microsoft.
I think I'll see which way the wind blows on the big day if this crops up :)
As of today, zone-redundant config is generally available for the Business Critical tier:
"Zone-redundant configuration is in public preview for the General Purpose service tier and generaly (sic) available for the Business Critical service tier."
Source: https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/high-availability-sla?view=azuresql-mi&preserve-view=true
"Azure SQL Database elastic pool" in the Premium and Business Critical service tiers of the Premium Availability model support both locally redundant and zone redundant availability. Premium and Business Critical service tier zone redundant availability is not available for SQL Managed Instance. Azure SQL Database with General Purpose supports zone redundant availability, but, the answer calls for "Single Azure SQL database", which won't work for this use case.
https://azure.microsoft.com/en-gb/blog/azure-sql-database-now-offers-zone-redundant-premium-databases-and-elastic-pools/#:~:text=To%20take%20advantage%20of%20this%20capability%2C%20you%20simply,reconfigure%20the%20database%20or%20pool%20without%20any%20downtime.
https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell#premium-and-business-critical-service-tier-locally-redundant-availability
"Zone-redundant configuration is not available in SQL Managed Instance. In SQL Database this feature is only available when the Gen5 hardware is selected."
upvoted 3 times
...
...
...
...
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.
GarryK
Highly Voted 2 years, 2 months agoStixxNSnares
1 year agoAdx_YT
3 months, 1 week agocb3f703
2 months ago_punky_
1 month, 2 weeks agoDeBoer
1 year, 9 months agoGarryK
1 year, 10 months agojoesatriani
Highly Voted 1 year, 2 months agoSeMo0o0o0o
Most Recent 3 weeks, 6 days agokodjoa2024
8 months, 3 weeks agojoesatriani
1 year, 2 months agoDarkeh
1 year, 3 months agobd1234
1 year, 9 months agodagomo
1 year, 10 months agoOPT_001122
1 year, 10 months agopkkalra
1 year, 10 months agoEXzw
1 year, 8 months agoMadball
1 year, 10 months agoMadball
1 year, 10 months agoGhoshy
1 year, 11 months ago[Removed]
1 year, 11 months agoRandomNickname
2 years agoRandomNickname
1 year, 10 months agotesttaker13
1 year, 10 months agoRandomNickname
1 year, 10 months agoFidel_104
9 months, 1 week agobp_a_user
4 months, 3 weeks agoRavi1383
2 years agoA_GEE
2 years agoA_GEE
2 years agoezfix
2 years, 2 months agoWolviet7
2 years, 2 months agoWolviet7
2 years, 2 months agontobars
2 years, 2 months ago