Free AZ-305 Exam Braindumps
Designing Microsoft Azure Infrastructure Solutions Questions 30–34 (page: 30)

Updated On: 16-Nov-2026
View Related Case Study

You have an on-premises server named Server1 that runs Windows Server and contains a Microsoft SQL Server database named DB1.
You have an Azure subscription.
You plan to migrate DB1 to Azure.
You use the Azure Database Migration Service to assess DB1 and receive the assessment results shown in the following table.

You need to recommend a migration target for DB1. The migration target must meet the following requirements:
-Eliminate the need for post-migration operating system maintenance.
-Minimize administrative effort to prepare for the migration.
What should you recommend?

  1. Azure Cosmos DB for NoSQL
  2. SQL Server on Azure Virtual Machines
  3. Azure Cosmos DB for PostgreSQL
  4. Azure SQL Managed Instance
  5. Azure SQL Database

Answer(s): D

Explanation:

SQL Server to Azure SQL Managed Instance
Azure SQL Managed Instance is a recommended target option for SQL Server workloads that require a fully managed service without having to manage virtual machines or their operating systems. SQL Managed Instance enables you to move your on-premises applications to Azure with minimal application or database changes. It offers complete isolation of your instances with native virtual network support.
Incorrect:
[Not B]
If one of the following conditions applies to your business, consider moving to a SQL Server virtual machine (VM) instead:
*-> You require direct access to the operating system or file system, such as to install third-party or custom agents on the same virtual machine with SQL Server.


Reference:

https://learn.microsoft.com/en-us/data-migration/sql-server/managed-instance/overview



View Related Case Study

You have an Azure subscript ion that contains 10 Azure SQL databases in an elastic pool. Each database is 600 GB.
You need to ensure that you can increase the size of each database to 15 TB. The solution must minimize database downtime.
What should you do?

  1. Enable geo-replication for each database.
  2. Remove the elastic pool. Update each database to the Hyperscale service tier.
  3. Update the elastic pool to the Premium service tier.
  4. Remove the elastic pool. Update each database to the Business Critical service tier.

Answer(s): B

Explanation:

To increase the size of your databases to 15 TB while maintaining minimum downtime, you must migrate your elastic pool to the Azure SQL Database Hyperscale service tier. Traditional Azure SQL service tiers (Basic, Standard, Premium, and General Purpose/Business Critical vCore) cap single or pooled database sizes at 4 TB. Only the Hyperscale tier supports up to 100 TB per database inside an elastic pool (and 128 TB for single databases).
Because Hyperscale architecture decouples compute from storage, this transition can be executed seamlessly with minimal disruption.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tier-hyperscale-frequently-asked-questions -faq



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription.
You need to deploy a solution that will provide point-in-time restore for blobs in storage accounts that have blob versioning and blob soft delete enabled.
Which type of blob should you create, and what should you enable for the accounts? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Block
Point-in-time restore for block blobs
Point-in-time restore provides protection against accidental deletion or corruption by enabling you to restore block blob data to an earlier state. Point-in-time restore is useful in scenarios where a user or application accidentally deletes data or where an application error corrupts data. Point-in-time restore also enables testing scenarios that require reverting a data set to a known state before running further tests.
Point-in-time restore is supported for general-purpose v2 storage accounts in the standard performance tier only. Only data in the hot and cool access tiers can be restored with point-in-time restore.
Box 2: The change feed
Enable and configure point-in-time restore
Before you enable and configure point-in-time restore, enable its prerequisites for the storage account: soft delete, change feed, and blob versioning.


Reference:

https://learn.microsoft.com/en-us/azure/storage/blobs/point-in-time-restore-overview



View Related Case Study

You are planning an Azure IoT Hub solution that will include 50,000 IoT devices.
Each device will stream data, including temperature, device ID, and time data. Approximately 50,000 records will be written every second. The data will be visualized in near real time.
You need to recommend a service to store and query the data.
Which two services can you recommend? Each correct answer presents a complete solution.
Note: Each correct selection is worth one point.

  1. Azure Table Storage
  2. Azure Event Grid
  3. Azure Cosmos DB SQL API
  4. Azure Time Series Insights

Answer(s): C,D

Explanation:

D: Time Series Insights is a fully managed service for time series data. In this architecture, Time Series Insights performs the roles of stream processing, data store, and analytics and reporting. It accepts streaming data from either IoT Hub or Event Hubs and stores, processes, analyzes, and displays the data in near real time.
C: The processed data is stored in an analytical data store, such as Azure Data Explorer, HBase, Azure Cosmos DB, Azure Data Lake, or Blob Storage.


Reference:

https://docs.microsoft.com/en-us/azure/architecture/data-guide/scenarios/time-series



View Related Case Study

You need to design a highly available Azure SQL database that meets the following requirements:
-Failover between replicas of the database must occur without any data loss.
-The database must remain available in the event of a zone outage.
-Costs must be minimized.
Which deployment option should you use?

  1. Azure SQL Database Business Critical
  2. Azure SQL Managed Instance Business Critical
  3. Azure SQL Database Standard
  4. Azure SQL Database Hyperscale

Answer(s): A

Explanation:

To design a highly available Azure SQL database that meets the specific requirements:
Failover without any data loss: The Business Critical tier in Azure SQL Database uses a high availability model with synchronous data replication to multiple replicas, ensuring zero data loss during failover. This is essential for your requirement of no data loss.
Available during a zone outage: The Business Critical service tier supports Zone Redundant Configuration, allowing you to place replicas in different availability zones, ensuring the database remains available even if a zone experiences an outage.
Cost minimization: While Azure SQL Database Business Critical is more expensive than other options like Standard or Hyperscale, it offers a balance between high availability and the required zero data loss. Other options like Managed Instance Business Critical would be more costly because of additional features beyond what's needed here, such as more extensive SQL Server instance-level features.
Here’s why other options don't fit as well:
Azure SQL Managed Instance Business Critical: This also offers zero data loss and high availability, but it is costlier than the standalone Azure SQL Database.
Azure SQL Database Standard: This is a lower-cost option but doesn’t guarantee zero data loss or provide zone redundancy.
Azure SQL Database Hyperscale: Hyperscale is designed for massive scale but doesn’t natively support zone redundancy or zero-data-loss failover as well as Business Critical.



Viewing page 30 of 78
Viewing questions 146 - 150 out of 382 questions


Post your Comments and Discuss Microsoft AZ-305 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!