Free AZ-305 Exam Braindumps
Designing Microsoft Azure Infrastructure Solutions Questions 20–24 (page: 28)

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

You have an Azure subscription.
Your on-premises network contains a file server named Server1. Server1 stores 5 TB of company files that are accessed rarely.
You plan to copy the files to Azure Storage.
You need to implement a storage solution for the files that meets the following requirements:
-The files must be available within 24 hours of being requested.
-Storage costs must be minimized.
Which two possible storage solutions achieve this goal? Each correct answer presents a complete solution.
Note: Each correct selection is worth one point.

  1. Create an Azure Blob Storage account that is configured for the Cool default access tier. Create a blob container, copy the files to the blob container, and set each file to the Archive access tier.
  2. Create a BlockBlobStorage storage account. Create a blob container and copy the files to the blob container.
  3. Create a general-purpose v2 storage account that is configured for the Cool default access tier. Create a file share in the storage account and copy the files to the file share.
  4. Create a general-purpose v2 storage account that is configured for the Hot default access tier. Create a blob container, copy the files to the blob container, and set each file to the Archive access tier.
  5. Create a FileStorage storage account. Create a file share in the storage account and copy the files to the file share.

Answer(s): A,D

Explanation:

To minimize costs: The Archive tier is optimized for storing data that is rarely accessed and stored for at least 180 days with flexible latency requirements (on the order of hours).
[A]
This solution is highly effective and is considered an industry-standard approach for minimizing storage costs for rarely accessed data in Azure.
By configuring your blobs to the Archive access tier, you leverage the lowest possible storage cost per GB. Since your requirement allows for a 24-hour retrieval window, the latency associated with "rehydrating" data from the Archive tier—which typically takes a few hours—is perfectly acceptable.
Why This Strategy Works
Cost Efficiency: The Archive tier offers the lowest storage rates in Azure.
While you do pay more for data retrieval and transaction operations, this is the optimal trade-off for data you rarely need to access.
Meeting Your Requirements: Because the Archive tier allows for retrieval within "hours," you are well within your 24-hour requirement.
Granular Control: As noted, you can set individual blobs to the Archive tier regardless of the storage account's default tier (Hot or Cool). This gives you the flexibility to mix data types within the same container if needed.
[D]
That solution works and meets your requirements. Moving the data to the Archive access tier within a General-purpose v2 account is the most cost-effective way to store rarely used data.
Here is why this fits:
Minimized Cost: The Archive tier has the lowest storage costs available in Azure.
Availability: While the data is "offline," it can be rehydrated back to the Hot or Cool tier. Standard rehydration typically completes within 15 hours, fitting well inside your 24-hour window.
Simplicity: Using a standard blob container allows for easy management and direct uploads.


Reference:

https://azure.microsoft.com/en-ca/products/storage https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-storage-tiers



View Related Case Study

You have an app named App1 that uses an Azure Blob Storage container named app1data.
App1 uploads a cumulative transaction log file named File1.txt to a block blob in app1data once every hour. File1.txt only stores transaction data from the current day.
You need to ensure that you can restore the last uploaded version of File1.txt from any day for up to 30 days after the file was overwritten. The solution must minimize storage space.
What should you include in the solution?

  1. container soft delete
  2. blob snapshots
  3. blob soft delete
  4. blob versioning

Answer(s): D

Explanation:

You can enable Blob storage versioning to automatically maintain previous versions of a blob when it is modified or deleted.
When blob versioning is enabled, then you can restore an earlier version of a blob to recover your data if it is erroneously modified or deleted.
Note: To enable blob versioning for a storage account in the Azure portal:
1. Navigate to your storage account in the portal.
2. Under Data management, choose Data protection.
3. In the Tracking section, select Enable versioning for blobs, and then choose whether to keep all versions or delete them after a period of time.

Incorrect:
Not B: Blob versioning and blob snapshots
A blob snapshot is a read-only copy of a blob that's taken at a specific point in time. Blob snapshots and blob versions are similar, but a snapshot is created manually by you or your application, while a blob version is created automatically on a write or delete operation when blob versioning is enabled for your storage account.


Reference:

https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-enable



View Related Case Study

You have an Azure subscription.
You plan to deploy an app that will store data across multiple databases.
You need to recommend a storage solution for the app. The solution must meet the following requirements:
-Ensure that queries can be executed simultaneously across all the databases.
-Minimize development effort.
-Minimize query latency.
What should you include in the recommendation?

  1. SQL Server on Azure Virtual Machines
  2. Azure SQL Edge
  3. Azure SQL Database
  4. Azure SQL Managed Instance

Answer(s): C

Explanation:

Azure SQL Database elastic query
Applies to: Azure SQL Database
The elastic query feature (in preview) enables you to run a Transact-SQL (T-SQL) query that spans multiple databases in Azure SQL Database. It allows you to perform cross-database queries to access remote tables, and to connect Microsoft and third-party tools (Excel, Power BI, Tableau, etc.) to query across data tiers with multiple databases. Using this feature, you can scale out queries to large data tiers and visualize the results in business intelligence (BI) reports.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-query-overview



View Related Case Study

You have an app named App1 that uses two on-premises Microsoft SQL Server databases named DB1 and DB2.
You plan to migrate DB1 and DB2 to Azure
You need to recommend an Azure solution to host DB1 and DB2. The solution must meet the following requirements:
-Support server-side transactions across DB1 and DB2.
-Minimize administrative effort.
What should you recommend?

  1. two Azure SQL databases in an elastic pool
  2. two databases on the same Azure SQL managed instance
  3. two databases on the same SQL Server instance on an Azure virtual machine
  4. two Azure SQL databases on different Azure SQL Database servers

Answer(s): B

Explanation:

Elastic database transactions for Azure SQL Database and Azure SQL Managed Instance allow you to run transactions that span several databases.
SQL Managed Instance enables system administrators to spend less time on administrative tasks because the service either performs them for you or greatly simplifies those tasks.


Reference:

https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-transactions-overview?view=azuresql



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription.
You need to deploy a relational database. The solution must meet the following requirements:
-Support multiple read-only replicas.
-Automatically load balance read-only requests across all the read-only replicas.
-Minimize administrative effort
What should you use? 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: A single Azure SQL database
Service
Hyperscale allows for 1-4 secondaries (1 by default).
If more than one secondary replica is present, the workload is distributed across all available secondaries.
Note: As part of High Availability architecture, each single database or elastic pool database in the Premium and Business Critical service tier is automatically provisioned with a primary read-write replica and one or more secondary read-only replicas. The secondary replicas are provisioned with the same compute size as the primary replica. The read scale-out feature allows you to offload read-only workloads using the compute capacity of one of the read-only replicas, instead of running them on the read-write replica. This way, some read-only workloads can be isolated from the read-write workloads, and don't affect their performance. The feature is intended for the applications that include logically separated read-only workloads, such as analytics. In the Premium and Business Critical service tiers, applications could gain performance benefits using this additional capacity at no extra cost.
Box 2: Hyperscale
Service tier
In Premium and Business Critical service tiers, only one of the read-only replicas is accessible at any given time. Hyperscale supports multiple read-only replicas.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/database/read-scale-out?view=azuresql



Viewing page 28 of 78
Viewing questions 136 - 140 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!