AZ-305 Practice Test 47 — 15 Questions

Question 1

A global e-commerce company needs a database solution that can handle high-velocity writes from user transactions across multiple regions. They require multi-region writes with automatic conflict resolution and single-digit millisecond latency for reads and writes. Which Azure data store should they use?

Accepted Answer

Azure Cosmos DB. Azure Cosmos DB is the correct choice because it offers multi-region writes with automatic conflict resolution using last-writer-wins (LWW) or custom conflict resolution policies, and it guarantees single-digit millisecond latency for both reads and writes at the 99th percentile. Its globally distributed, multi-model design is purpose-built for high-velocity transactional workloads that require active-active replication across regions.

Answer

Azure Table Storage

Answer

Azure SQL Database

Answer

Azure Redis Cache

Question 2

A global IoT platform ingests telemetry data from millions of devices. The application requires multi-region writes to support low-latency ingestion from any location. The schema uses JSON documents and fields often vary. The team needs automatic conflict resolution when the same document is updated concurrently from different regions. Additionally, read operations for device commands must use strong consistency, while user-facing dashboard queries can use eventual consistency. Which Azure Cosmos DB configuration should they choose?

Accepted Answer

Azure Cosmos DB with multi-master and per-request consistency override. Option C is correct because the scenario requires multi-region writes (multi-master) for low-latency ingestion, automatic conflict resolution (which multi-master provides via last-writer-wins or custom conflict resolvers), and strong consistency for device command reads while allowing eventual consistency for dashboards. Per-request consistency override in Azure Cosmos DB lets the application set strong consistency on specific read operations (e.g., device commands) while defaulting to eventual consistency for others, meeting all requirements without sacrificing performance.

Answer

Azure Cosmos DB with single-master and multiple read regions

Answer

Azure Cosmos DB with multi-master and default strong consistency

Answer

Azure Cosmos DB with multi-master and eventual consistency only

Question 3

Drag and drop the steps to implement Azure Traffic Manager for geographic routing into the correct order.

Question 4

Drag and drop the steps to deploy a web app using Azure App Service with a custom domain and SSL certificate into the correct order.

Question 5

A company uses Microsoft Entra ID (Microsoft Entra ID). They need to automate the process of granting users access to a specific application only during business hours and revoking it automatically. The access should be based on a request-approval workflow. Which Microsoft Entra ID feature should they use?

Accepted Answer

Entitlement Management. Entitlement Management (D) is correct because it provides automated access lifecycle management through access packages, which can include time-bound assignments (e.g., business hours) and require approval workflows. This allows you to define policies that grant access to the application only during specified hours and automatically revoke it when the policy expires or conditions change, without manual intervention.

Answer

Privileged Identity Management (PIM)

Answer

Conditional Access

Answer

Access Reviews

Question 6

A company ingests IoT sensor data into Azure Blob Storage. Data is written frequently and is accessed rarely after the first 24 hours. The company must retain the data for exactly 90 days for compliance. They want to minimize storage costs by automatically moving data to the cheapest possible storage tier as soon as possible. Which Azure Blob Storage lifecycle management policy should they implement?

Accepted Answer

Move to Cool tier after 1 day, delete after 90 days. Option A is correct because the data is rarely accessed after 24 hours, so moving it to Cool tier after 1 day minimizes cost while still allowing low-latency access. The 90-day deletion aligns with the compliance retention requirement. Cool tier is the cheapest online tier, and moving data there as soon as possible (after 1 day) reduces costs without incurring the early deletion penalty or retrieval latency of Archive tier.

Answer

Move to Archive tier after 1 day, delete after 90 days

Answer

Move to Cool tier after 30 days, delete after 90 days

Answer

Move to Archive tier after 30 days, delete after 90 days

Question 7

Drag and drop the steps to migrate an on-premises SQL Server database to Azure SQL Database using the Data Migration Assistant (DMA) into the correct order.

Question 8

A global e-commerce platform requires a database that supports multi-region writes with automatic conflict resolution and single-digit millisecond latency for reads and writes from any region. The application uses a flexible schema with JSON documents. They also need to enforce strong consistency for critical operations (e.g., order placement) while allowing eventual consistency for less critical reads. Which Azure data service and configuration should they choose?

Accepted Answer

Azure Cosmos DB with multi-region writes enabled on the account, using the SQL (Core) API, and applying strong consistency for the order placement operation via RequestOptions.. Azure Cosmos DB with multi-region writes enabled and the SQL (Core) API meets all requirements: it supports multi-region writes with automatic conflict resolution (last-writer-wins or custom), offers single-digit millisecond latency for reads and writes from any region, and uses a flexible JSON document schema. The ability to enforce strong consistency for critical operations like order placement via RequestOptions (using session or strong consistency at the request level) while allowing eventual consistency for less critical reads directly addresses the mixed consistency needs.

Answer

Azure SQL Database with active geo-replication across two regions and failover groups.

Answer

Azure Cache for Redis with geo-replication.

Answer

Azure Table Storage with geo-redundant storage (GRS) and read-access (RA-GRS).

Question 9

A company needs to store massive amounts of unstructured data, such as images and videos, for a media processing application. The data must be accessible via REST APIs and support tiered storage for cost optimization. Which Azure storage solution should they use?

Accepted Answer

Azure Blob Storage. Azure Blob Storage is the correct choice because it is designed for massive amounts of unstructured data (images, videos) and provides REST API access via HTTP/HTTPS. It also supports tiered storage (Hot, Cool, Cold, Archive) to optimize costs based on data access patterns, making it ideal for media processing workloads.

Answer

Azure Files

Answer

Azure Data Lake Storage Gen2

Answer

Azure Disk Storage

Question 10

A company needs a data storage solution for a global application that frequently accesses recent data and less frequently older data. Data is unstructured blobs. They want to automatically move blobs to cool storage after 30 days and to archive storage after 90 days. Additionally, blobs must be retained for 7 years and cannot be deleted or modified during that period. Which Azure Blob Storage features should they combine?

Accepted Answer

Use blob lifecycle management policies and time-based retention policies.. Option B is correct because blob lifecycle management policies automatically transition blobs from hot to cool after 30 days and to archive after 90 days, while time-based retention policies enforce immutability for a fixed period (7 years), preventing deletion or modification. This combination meets both the tiering and retention requirements without manual intervention.

Answer

Use blob lifecycle management policies and legal hold (immutable blobs).

Answer

Use Azure Storage Analytics and immutability policies.

Answer

Use Azure File Sync and lifecycle management.

Question 11

A company ingests IoT sensor data into Azure Blob Storage. Data is written frequently and accessed rarely after the first 24 hours. The company must retain the data for exactly 90 days for compliance. They want to minimize storage costs by automatically moving data to cheaper tiers as soon as possible. Which lifecycle management policy should they implement?

Accepted Answer

Move to Cool tier after 1 day and then to Archive after 30 days. Option B is correct because it aligns with the access pattern: data is frequently accessed only in the first 24 hours, so moving to Cool tier after 1 day (when access drops) saves costs, then moving to Archive after 30 days meets the 90-day retention requirement while minimizing storage costs. The lifecycle policy must ensure data is not moved to Archive before the compliance period ends, and moving to Cool immediately (0 days) would incur unnecessary write costs for frequently written data.

Answer

Move to Cool tier immediately (0 days) and then to Archive after 30 days

Answer

Move to Archive tier after 1 day

Answer

Move to Cool tier after 30 days and to Archive after 90 days

Question 12

A company manages a fleet of millions of IoT devices that send telemetry data every minute. The data must be stored for 10 years to meet compliance requirements. For the first 30 days, data is accessed frequently for real-time dashboards and alerting. After 30 days, data is only accessed occasionally for historical analysis and reporting. The solution must be cost-effective and support high ingestion rates. Which Azure service should the company use to store and query this data?

Accepted Answer

Azure Data Explorer. Azure Data Explorer (ADX) is designed for high-ingestion, time-series telemetry data and supports real-time dashboards and alerting on fresh data, while also providing cost-effective long-term storage for historical queries. Its columnar storage and indexing enable fast analytics on billions of records, making it ideal for IoT scenarios with millions of devices sending data every minute and a 10-year retention requirement.

Answer

Azure Blob Storage with Azure Data Lake Storage Gen2

Answer

Azure SQL Database

Answer

Azure Cosmos DB with SQL API

Question 13

A company needs a fully managed NoSQL database for a new application with a key-value and document data model. They require single-digit millisecond latency at any scale, multi-region writes with automatic conflict resolution, and a serverless capacity option to handle unpredictable traffic. Which Azure data service should they use?

Accepted Answer

Azure Cosmos DB. Azure Cosmos DB is the correct choice because it is a fully managed NoSQL database that supports both key-value and document data models natively. It guarantees single-digit millisecond latency at any scale, offers multi-region writes with automatic conflict resolution via its multi-master replication, and provides a serverless capacity mode that automatically scales based on demand, making it ideal for unpredictable traffic.

Answer

Azure Table Storage

Answer

Azure Cache for Redis

Answer

Azure SQL Database

Question 14

A company needs to store large amounts of unstructured data (log files) for analytics. The data is accessed frequently for the first 30 days, then occasionally for the next 90 days, and rarely after that but must be retained for 7 years for compliance. The data must not be modified or deleted during the retention period, and administrative access must not be able to bypass this restriction. They want to minimize storage costs. Which combination of Azure Blob Storage features should they configure?

Accepted Answer

Configure a lifecycle management policy to move blobs to Cool tier after 30 days and to Archive tier after 120 days. Apply a time-based retention policy with a retention period of 2,555 days and lock it.. Option A is correct because it combines a lifecycle management policy to automatically transition blobs from Hot to Cool after 30 days and to Archive after 120 days, minimizing storage costs. The time-based retention policy with a locked retention period of 2,555 days (7 years) ensures that blobs cannot be modified or deleted during the retention period, and locking the policy prevents administrative bypass, meeting the compliance requirement.

Answer

Enable soft delete and versioning on the storage account, and use a custom script to delete blobs after 7 years. Manually move blobs to Cool and Archive tiers using Azure PowerShell.

Answer

Set each blob's access tier to Cool on upload, then manually change to Archive after 30 days. Enable Azure Backup on the storage account for retention.

Answer

Apply a legal hold on the container to prevent deletion, and configure a lifecycle policy to move blobs to Archive after 30 days.

Question 15

A company runs a high-throughput time-series workload that stores sensor data from IoT devices. Data is ingested at a rate of millions of events per second. The application requires low-latency queries (under 100 ms) on recent data (less than 30 days old) and the ability to run occasional analytical queries on historical data older than 30 days. The solution must automatically move cold data to a cost-optimized tier and provide built-in analytics. Which Azure service should they use?

Accepted Answer

Azure Time Series Insights (TSI). Azure Time Series Insights (TSI) is purpose-built for high-throughput IoT time-series data, supporting millions of events per second with sub-100 ms query latency on warm data (less than 30 days old). It automatically moves cold data to a cost-optimized warm/cold store and provides built-in analytics and visualization for time-series patterns, making it the ideal choice for this scenario.

Answer

Azure Cosmos DB with analytical store

Answer

Azure Event Hubs with Azure Data Lake Storage

Answer

Azure SQL Database with elastic query