Free AZ-305 Exam Braindumps
Designing Microsoft Azure Infrastructure Solutions Questions 45–49 (page: 33)

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

HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription that contains the logical SQL servers in Azure shown in the following table.

The subscription contains the storage accounts shown in the following table.

You create the Azure SQL databases shown in the following table.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Yes
Auditing works fine for a Standard account.
Box 2: No
Auditing limitations: Premium storage is currently not supported.
Box 3: No
Auditing limitations: Premium storage is currently not supported.


Reference:

https://docs.microsoft.com/en-us/azure/azure-sql/database/auditing-overview#auditing-limitations



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an on-premises app named App1 that stores data in a Microsoft SQL Server database named DB1. App1 uses cross-database transactions.
You plan to move App1 to Azure.
You need to recommend which services to use to host DB1 in Azure and migrate DB1 to Azure. The solution must meet the following requirements:
● Ensure that once App1 moves to Azure, DB1 users can authenticate by using their Microsoft Entra credentials.
● Minimize administrative effort to patch and update the database host once App1 moves to Azure.
● Minimize administrative effort during the migration of DB1 to Azure.
● Minimize costs.
What should you recommend? 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:




Azure SQL Managed Instance
Azure Database Migration Service
Azure SQL Managed Instance supports native cross-database transactions and Microsoft Entra authentication. Its managed platform handles operating system and database engine patching and upgrades, reducing administration while preserving SQL Server compatibility and minimizing application changes.
Azure Database Migration Service automates and coordinates migration from on-premises SQL Server to Azure SQL Managed Instance, minimizing manual migration work and the need for custom tooling.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/sql-managed-instance-paas-o verview?view=azuresql



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You are designing a data storage solution to support reporting.
The solution will ingest high volumes of data in the JSON format by using Azure Event Hubs. As the data arrives, Event Hubs will write the data to storage. The solution must meet the following requirements:
-Organize data in directories by date and time.
-Allow stored data to be queried directly, transformed into summarized tables, and then stored in a data warehouse.
-Ensure that the data warehouse can store 50 TB of relational data and support between 200 and 300 concurrent read operations.
Which service should you recommend for each type of data store? 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: Azure Data Lake Storage Gen2
Azure Data Explorer integrates with Azure Blob Storage and Azure Data Lake Storage (Gen1 and Gen2), providing fast, cached, and indexed access to data stored in external storage. You can analyze and query data without prior ingestion into Azure Data Explorer. You can also query across ingested and uningested external data simultaneously.
Azure Data Lake Storage is optimized storage for big data analytics workloads.
Use cases: Batch, interactive, streaming analytics and machine learning data such as log files, IoT data, click streams, large datasets
Box 2: Azure SQL Database Hyperscale
Azure SQL Database Hyperscale is optimized for OLTP and high throughput analytics workloads with storage up to 100TB.
A Hyperscale database supports up to 100 TB of data and provides high throughput and performance, as well as rapid scaling to adapt to the workload requirements. Connectivity, query processing, database engine features, etc. work like any other database in Azure SQL Database.
Hyperscale is a multi-tiered architecture with caching at multiple levels. Effective IOPS will depend on the workload.
Compare to:
General purpose: 500 IOPS per vCore with 7,000 maximum IOPS
Business critical: 5,000 IOPS with 200,000 maximum IOPS
Incorrect:
* Azure Synapse Analytics Dedicated SQL pool.
Max database size: 240 TB
A maximum of 128 concurrent queries will execute and remaining queries will be queued.


Reference:

https://docs.microsoft.com/en-us/azure/data-explorer/data-lake-query-data https://docs.microsoft.com/en-us/azure/azure-sql/database/service-tier-hyperscale https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-service-cap acity-limits



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an on-premises app named App1 that reads data from a table named Table1, writes new data to Table1, and scans Table1 for aggregate statistics. App1 uses hard-coded partition keys for all read and write operations.
You plan to migrate App1 to a new platform in Azure.
You need to recommend a solution that meets the following requirements:
-Provides the highest scalability and performance
-Minimizes development effort
What should you include in the recommendation for each requirement? 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: Azure table storage
Minimize development effort:
Using Azure Table storage can help minimize development effort, particularly if your current application uses a similar NoSQL key-value store or a "lift-and-shift" migration strategy is suitable.
Incorrect:
* Azure Cosmos DB Table API
To migrate an on-premises application that uses hard-coded partition keys to Azure while achieving the highest scalability and performance, you should migrate to Azure Cosmos DB and implement a synthetic partition key. However, because hard-coded keys often lead to "hot" partitions (where one physical server handles all traffic), you must re-architect the partitioning strategy during the migration to distribute the workload evenly.
Box 2: Azure Cosmos DB Table API
Provide the highest scalability and performance:
To migrate an on-premises application that uses hard-coded partition keys to Azure, use the rehosting (lift-and-shift) approach.
To migrate an on-premises application that uses hard-coded partition keys to Azure while achieving the highest scalability and performance, you should migrate to Azure Cosmos DB and implement a synthetic partition key.
1. Adopt a "Lift-and-Shift" Strategy
Migrate your application and data without modifying the existing code or architecture. This is the fastest way to move to the cloud when you want to avoid refactoring hard-coded logic.
Infrastructure: Host the application on Azure Virtual Machines (VMs) or Azure App Service. These services provide an environment similar to your on-premises setup, requiring no code changes to handle the hard-coded keys.
2. Choose a Compatible Data Store
To maintain the functionality of hard-coded partition keys without rewriting the data layer, migrate your database to a compatible Azure service:
*-> Azure Cosmos DB for Table: If your on-premises table uses a key-value or tabular structure, use Azure Cosmos DB for Table. It is wire-compatible with Azure Table storage, allowing the application to use the same hard-coded partition keys.
System-Defined Partition Keys: If you move to a partitioned container in Cosmos DB, Azure can provide a system-defined partition key (e.g., /_partitionKey) to support the migration of non-partitioned data, though using the latest SDK version is recommended.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/migrate-containers-partitioned-to-nonpartitioned https://docs.azure.cn/en-us/cosmos-db/nosql/synthetic-partition-keys



View Related Case Study

You plan to migrate on-premises MySQL databases to Azure Database for MySQL Flexible Server.
You need to recommend a solution for the Azure Database for MySQL Flexible Server configuration. The solution must meet the following requirements:
-The databases must be accessible if a datacenter fails.
-Costs must be minimized.
Which compute tier should you recommend?

  1. Burstable
  2. General Purpose
  3. Memory Optimized

Answer(s): B



Viewing page 33 of 78
Viewing questions 161 - 165 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!