Exam AZ-305 All Questions

View all questions & answers for the AZ-305 exam

Exam AZ-305 topic 2 question 8 discussion

Actual exam question from Microsoft's AZ-305

Question #: 8
Topic #: 2

HOTSPOT -
You have an on-premises database that you plan to migrate to Azure.
You need to design the database architecture to meet the following requirements:
✑ Support scaling up and down.
✑ Support geo-redundant backups.
✑ Support a database of up to 75 TB.
✑ Be optimized for online transaction processing (OLTP).
What should you include in the design? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:

Show Suggested Answer

Suggested Answer:

Box 1: Azure SQL Database -
Azure SQL Database:
Database size always depends on the underlying service tiers (e.g. Basic, Business Critical, Hyperscale).
It supports databases of up to 100 TB with Hyperscale service tier model.
Active geo-replication is a feature that lets you to 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 databases are also known as geo-secondaries, or geo-replicas.
Azure SQL Database and SQL Managed Instance enable you to dynamically add more resources to your database with minimal downtime.

Box 2: Hyperscale -
Incorrect Answers:
✑ SQL Server on Azure VM: geo-replication not supported.
✑ Azure Synapse Analytics is not optimized for online transaction processing (OLTP).
✑ Azure SQL Managed Instance max database size is up to currently available instance size (depending on the number of vCores).
Max instance storage size (reserved) - 2 TB for 4 vCores
- 8 TB for 8 vCores
- 16 TB for other sizes
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-overview https://medium.com/awesome-azure/azure-difference-between-azure-sql-database-and-sql-server-on-vm-comparison-azure-sql-vs-sql-server-vm-cf02578a1188

by Eltooth at Dec. 16, 2021, 5:44 a.m.

Comments

Submit Cancel

Syd

Highly Voted 3 years, 6 months ago

Answer is correct. -Azure SQL Database with Hyperscale(support up to 100TB). https://docs.microsoft.com/en-us/azure/azure-sql/database/service-tier-hyperscale#:~:text=A%20Hyperscale%20database%20is%20created%20with%20a%20starting,about%20Hyperscale%20pricing%2C%20see%20Azure%20SQL%20Database%20Pricing Managed Instance is incorrect because the database limit is 2-8TB max. https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/resource-limits#:~:text=Up%20to%20280%2C%20unless%20the%20instance%20storage%20size,TB%29%20and%20Azure%20Premium%20Disk%20storage%20allocation%20space.

upvoted 53 times

Amrx

2 years, 5 months ago

Azure SQL MI also does not support active geo replication.

upvoted 6 times

...

xRiot007

1 year, 5 months ago

The limit for MI is now 16 TB - still far away from 75 TB.

upvoted 1 times

...

Snownoodles

Highly Voted 3 years, 3 months ago

75T can only be supported by hyperscale.

upvoted 14 times

...

hajurbau

Most Recent 3 months, 3 weeks ago

Answer correct Managed instance can only support upto 32 GB - 16 TB

upvoted 1 times

...

Thanveer

8 months, 3 weeks ago

Answer : Azure SQL Database Hyperscale is the most suitable database architecture for the given requirements.

upvoted 1 times

...

malcubierre

1 year, 8 months ago

The key is that only Hyperscale can deal with 75 Tb, All other have limit of 4 Tb

upvoted 3 times

...

NotMeAnyWay

2 years, 4 months ago

Azure SQL Database Hyperscale: Support scaling up and down: The Hyperscale service tier supports scaling compute resources up and down based on your workload requirements. Support geo-redundant backups: It offers automatic backups with the ability to enable geo-redundant backups to ensure data durability in case of regional disasters. Support a database of up to 75 TB: Hyperscale supports databases up to 100 TB in size, which meets the requirement of 75 TB. Be optimized for online transaction processing (OLTP): Azure SQL Database Hyperscale is designed to handle OLTP workloads with high performance and low latency. In summary, you should include Azure SQL Database with the Hyperscale service tier in your database architecture design to meet all the listed requirements.

upvoted 12 times

...

zellck

2 years, 5 months ago

1. Azure SQL DB 2. Hyperscale https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tier-hyperscale?view=azuresql#what-are-the-hyperscale-capabilities The Hyperscale service tier in Azure SQL Database provides the following additional capabilities: - Support for up to 100 TB of database size. - Higher overall performance due to higher transaction log throughput and faster transaction commit times regardless of data volumes. - Rapid Scale up - you can, in constant time, scale up your compute resources to accommodate heavy workloads when needed, and then scale the compute resources back down when not needed.

upvoted 5 times

...

omerco61

2 years, 5 months ago

Answer is correct; let me compare with explain on microsoft official site; https://learn.microsoft.com/en-us/training/modules/design-data-storage-solution-for-relational-data/4-design-for-sql-server-azure#:~:text=SQL%20Server%20licenses.-,Compare%20Azure%20SQL%20deployment%20options,-You%27ve%20reviewed%20the

upvoted 1 times

...

OPT_001122

2 years, 6 months ago

Answer is correct Box 1: Azure SQL Database Box 2: Hyperscale - key point 75TB Azure SQL Database with Hyperscale Thanks all who have mentioned the exam dates

upvoted 6 times

...

Ghoshy

2 years, 7 months ago

Exam Question 12/28/2022

upvoted 7 times

...

NarasimhanMV

2 years, 8 months ago

Ans - Correct

upvoted 2 times

...

jellybiscuit

2 years, 10 months ago

Correct. Resource limits for SQL Database tiers https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tier-hyperscale?view=azuresql#compare-resource-limits

upvoted 1 times

...

catfood

2 years, 11 months ago

"Support geo-redundant backups". - this is not the same as geo replication as the answer states.... Both MI and SQL variants have auto backup that is stored as geo redundant blobs replicated to a paired region. But yes, hyperscale is correct due to DB size.

upvoted 1 times

...

tictaclu

3 years ago

The reason to choose Hyperscale, since its the design of db migration: The Hyperscale service tier in Azure SQL Database provides the following additional capabilities: Support for up to 100 TB of database size. Fast database backups (based on file snapshots stored in Azure Blob storage) regardless of size with no IO impact on compute resources. Fast database restores (based on file snapshots) in minutes rather than hours or days (not a size of data operation). Higher overall performance due to higher transaction log throughput and faster transaction commit times regardless of data volumes. Rapid scale out - you can provision one or more read-only replicas for offloading your read workload and for use as hot-standbys. Rapid Scale up - you can, in constant time, scale up your compute resources to accommodate heavy workloads when needed, and then scale the compute resources back down when not needed.

upvoted 5 times

...