1. A company is developing a new application that will store highly sensitive customer data, including personally identifiable information (PII), in Azure Blob Storage. The company has a strict security policy requiring that all data at rest be encrypted using customer-managed keys (CMK) for enhanced control and compliance. The application will use a .NET SDK to interact with Azure Blob Storage.
Develop for Azure storage
A.Configure the storage account to use customer-managed keys from Azure Key Vault and assign a default encryption scope.
B.Enable Azure Storage Service Encryption (SSE) with platform-managed keys on the storage account.
C.Set the default encryption scope on the storage account to use a Microsoft-managed key.
D.Implement client-side encryption in the application before uploading data to Azure Blob Storage.
Show answerAnswer
A. Configure the storage account to use customer-managed keys from Azure Key Vault and assign a default encryption scope.
To meet the requirement of using customer-managed keys (CMK) for data at rest encryption in Azure Blob Storage, the storage account must be configured to integrate with Azure Key Vault. Assigning a default encryption scope ensures that all new blobs uploaded without specifying an encryption scope will automatically use the CMK.
2. A developer needs to store highly sensitive customer documents in Azure Blob Storage. These documents must be encrypted at rest and in transit. The company's security policy mandates that encryption keys must be managed by the customer, not by Microsoft. Which encryption option should the developer choose?
Develop for Azure storage
A.Microsoft-managed keys for Azure Storage encryption
B.Client-side encryption with Azure Storage SDK
C.Customer-managed keys with Azure Key Vault
D.Encryption scopes
Show answerAnswer
C. Customer-managed keys with Azure Key Vault
Customer-managed keys (CMK) with Azure Key Vault allow the customer to control the lifecycle of their encryption keys, satisfying the requirement that Microsoft does not manage them. Azure Storage still performs the encryption, but using keys provided by the customer.
3. A company is developing a new application that stores large binary files, such as images and videos. The application requires the ability to retain previous versions of these files whenever they are modified or deleted, allowing for point-in-time recovery and compliance auditing. Which Azure Blob Storage feature should be enabled to meet this requirement?
Develop for Azure storage
A.Change feed for Blob Storage
B.Immutable storage
C.Blob versioning
D.Soft delete for blobs
Show answerAnswer
C. Blob versioning
Blob versioning automatically creates a new version of a blob each time it's modified or deleted. This allows you to restore previous states of the blob and audit changes over time, directly addressing the requirement for retaining previous versions.
4. A company is migrating an on-premises application that uses a shared file system to store configuration files and user-generated content. The application requires SMB protocol access and needs to be accessible from multiple Azure Virtual Machines within the same region. The solution must provide high availability and be managed by Azure. Which Azure storage solution should the company use?
Develop for Azure storage
A.Azure Disk Storage
B.Azure Blob Storage
C.Azure NetApp Files
D.Azure Files
Show answerAnswer
D. Azure Files
Azure Files provides fully managed file shares in the cloud that are accessible via the industry-standard Server Message Block (SMB) protocol. This allows existing applications that rely on shared file systems to migrate easily without requiring code changes, and it's highly available within a region.
5. A global e-commerce platform uses Azure Cosmos DB for its product catalog. The platform experiences peak traffic during global sales events, requiring extremely low latency reads for product details from users worldwide. Updates to the product catalog are infrequent. To ensure the lowest possible read latency globally, which Cosmos DB configuration should be prioritized?
Develop for Azure storage
A.Enabling multi-region writes across all regions.
B.Increasing the provisioned throughput (RUs/s) in the primary region.
C.Distributing read replicas to all regions where users are located.
D.Configuring the account with Strong consistency.
Show answerAnswer
C. Distributing read replicas to all regions where users are located.
To achieve the lowest possible read latency for globally distributed users, data must be physically close to them. Distributing read replicas to all user-facing regions ensures that reads are served from the closest replica, minimizing network latency. While other options contribute to performance or consistency, direct data proximity is paramount for 'extremely low latency reads globally'.
6. An application is designed to store sensor data from IoT devices. The data is high-volume, time-series, and unstructured JSON documents. The development team needs a NoSQL database that can handle millions of small writes per second, provide flexible schema, and allow for efficient querying of time-series data.
Develop for Azure storage
A.Azure SQL Database
B.Azure Cosmos DB for NoSQL (Core) API
C.Azure Table Storage
D.Azure Database for PostgreSQL
Show answerAnswer
B. Azure Cosmos DB for NoSQL (Core) API
Azure Cosmos DB for NoSQL (Core) API is a globally distributed, multi-model database service that supports schema-less JSON documents. Its ability to handle high throughput, flexible schema, and robust querying makes it an excellent choice for high-volume, time-series IoT data.
7. A financial application uses Azure Cosmos DB for its transaction history. The application requires that all reads reflect the most recent write, regardless of the user's geographical location. Data consistency is paramount, even if it means slightly higher latency for read operations. Which Cosmos DB consistency model should be configured?
Develop for Azure storage
A.Session
B.Consistent Prefix
C.Eventual
D.Strong
Show answerAnswer
D. Strong
Strong consistency guarantees that all reads reflect the most recent write across all regions. While it can introduce higher latency, it ensures data is always up-to-date, meeting the requirement for 'all reads reflect the most recent write' and 'data consistency is paramount'.
8. A developer is implementing a feature that requires a temporary, shared storage for small, structured messages that need to be processed asynchronously by multiple worker roles. The messages should be simple text and not exceed 64 KB in size. The solution needs to be highly available and durable, but the order of processing is not strictly critical. Which Azure storage service is the most appropriate and cost-effective for this scenario?
Develop for Azure storage
A.Azure Service Bus Queues
B.Azure Event Hubs
C.Azure Cosmos DB
D.Azure Queue Storage
Show answerAnswer
D. Azure Queue Storage
Azure Queue Storage is a simple, highly scalable, and durable message queuing service ideal for storing large numbers of small, text-based messages for asynchronous processing. It's cost-effective for basic message queuing where strict ordering or advanced enterprise messaging features are not required.
9. A global e-commerce platform uses Azure Cosmos DB for its product catalog. The platform experiences high read traffic from users worldwide. To minimize latency for read operations, the company has configured Cosmos DB with multiple read regions. How can the application code ensure that read requests are consistently directed to the closest available replica?
Develop for Azure storage
A.Configure the Cosmos DB client with `ConnectionMode.Direct` and let the SDK handle geo-spatial routing.
B.Set the `PreferredLocations` property in the Cosmos DB client configuration to an ordered list of desired regions.
C.Manually specify the preferred read region in the Cosmos DB client configuration for each user's request.
D.Use `ConnectionMode.Gateway` and rely on Azure Traffic Manager for automatic routing to the nearest replica.
Show answerAnswer
B. Set the `PreferredLocations` property in the Cosmos DB client configuration to an ordered list of desired regions.
The `PreferredLocations` property in the Cosmos DB client configuration allows specifying an ordered list of regions. The SDK automatically detects the user's geographical location and attempts to connect to the closest preferred region for read operations, falling back to others if necessary.
10. A company stores customer profile data in Azure Table Storage. Each customer profile has a unique CustomerID and is associated with a Region. Queries frequently involve retrieving a specific customer's profile by CustomerID and also retrieving all customers within a specific Region. To optimize both query types, what is the most effective way to design the PartitionKey and RowKey for the table?
Develop for Azure storage
A.PartitionKey = CustomerID, RowKey = Region
B.PartitionKey = CustomerID + Region (composite), RowKey = CustomerID
PartitionKey = Region allows efficient retrieval of all customers within a region. RowKey = CustomerID, when combined with the PartitionKey, enables efficient point queries for a specific customer. Azure Table Storage queries on RowKey within a PartitionKey are very fast.
11. A developer is building a .NET application that needs to list all blobs within a specific virtual directory (folder) in an Azure Blob Storage container. The virtual directory structure is 'category/subcategory/item.jpg'. The developer wants to retrieve only the blobs under 'images/thumbnails/'.
Develop for Azure storage
A.Use the `GetBlobs` method and filter the results client-side after retrieval.
B.Use the `GetBlobs` method with the `delimiter` parameter set to '/'.
C.Use the `GetBlobs` method with the `prefix` parameter set to 'images/thumbnails/'.
D.Use the `GetBlobs` method without any parameters.
Show answerAnswer
C. Use the `GetBlobs` method with the `prefix` parameter set to 'images/thumbnails/'.
To efficiently list blobs within a specific virtual directory, the `GetBlobs` method (or its equivalent in other SDKs) should be used with the `prefix` parameter. Setting the `prefix` to 'images/thumbnails/' will instruct Azure Blob Storage to return only blobs whose names start with that string, effectively listing contents of the virtual directory.
12. A web application uses Azure Cosmos DB for its product catalog. The application frequently performs point reads (retrieving a single item by its ID) and range queries (retrieving items within a category). To minimize latency and ensure high availability, the Cosmos DB account is configured for multi-region writes. The product catalog data is updated infrequently but read very often. Which consistency level should be configured for the Cosmos DB account to balance strong consistency for writes with low-latency reads, while still allowing for some eventual consistency during failovers?
Develop for Azure storage
A.Bounded Staleness
B.Eventual
C.Session
D.Strong
Show answerAnswer
A. Bounded Staleness
Bounded Staleness offers a good balance. It guarantees that reads will not lag behind writes by more than 'K' versions or 'T' time interval. This provides stronger consistency than Session or Eventual, ensuring data isn't too stale, while still allowing for lower latency and higher throughput than Strong consistency, especially in a multi-region write environment where some eventual consistency is acceptable during propagation. Strong consistency would incur higher latency for reads in multi-region setups, and Session/Eventual might be too lax for 'infrequently updated but read very often' data where staleness needs to be bounded.
13. A developer needs to store unstructured sensor data (JSON format) from IoT devices into Azure. The data arrives at extremely high volume and velocity, and queries will primarily involve filtering and aggregating data based on timestamps and device IDs. The solution must support rapid ingestion and flexible schema. Which Azure storage service is best suited for this scenario?
Develop for Azure storage
A.Azure Cosmos DB
B.Azure Table Storage
C.Azure SQL Database
D.Azure Blob Storage
Show answerAnswer
A. Azure Cosmos DB
Azure Cosmos DB is a globally distributed, multi-model database service that is excellent for high-volume, high-velocity data ingestion like IoT. Its schema-agnostic nature (for NoSQL APIs) and strong indexing capabilities support flexible schema and efficient filtering/aggregation of JSON data.
14. A developer is designing a new microservices-based application that needs to store infrequently accessed, unstructured data, such as archived documents and historical logs. The data must be highly durable and cost-effective for long-term retention, with occasional retrieval needs. Which Azure Storage solution is most appropriate for this scenario?
Develop for Azure storage
A.Azure Queue Storage
B.Azure Files
C.Azure Table Storage
D.Azure Blob Storage (Archive Tier)
Show answerAnswer
D. Azure Blob Storage (Archive Tier)
Azure Blob Storage's Archive tier is specifically designed for rarely accessed, long-term data retention at the lowest cost, making it ideal for archived documents and historical logs with occasional retrieval.
15. An application uses Azure Blob Storage to store millions of small log files (average size 10 KB). These files are rarely accessed after the first 30 days but must be retained for compliance reasons for 7 years. Retrieving these files can tolerate several hours of delay. To minimize storage costs, which Blob Storage access tier should you configure for files older than 30 days?
Develop for Azure storage
A.Cool
B.Premium
C.Archive
D.Hot
Show answerAnswer
C. Archive
The Archive tier is optimized for rarely accessed data that can tolerate several hours of retrieval latency. It offers the lowest storage costs but the highest access costs and latency, making it ideal for long-term retention of infrequently accessed data like compliance logs.
16. A company is developing a new application that processes high volumes of sensor data from IoT devices. The data arrives as JSON documents, needs to be stored with low latency, and requires flexible schema capabilities. The application frequently queries this data using arbitrary attributes. Which Azure Cosmos DB API is most suitable for this scenario?
Develop for Azure storage
A.Cassandra API
B.MongoDB API
C.Gremlin API
D.Core (SQL) API
Show answerAnswer
D. Core (SQL) API
The Core (SQL) API in Azure Cosmos DB is ideal for JSON documents, offering flexible schema, low latency, and robust querying capabilities using a SQL-like language for arbitrary attributes, which perfectly suits sensor data processing.
17. A developer is implementing a new feature for a web application that allows users to upload large video files. These files need to be stored securely and made available for streaming after processing. During the upload process, the application must ensure data integrity and prevent corruption. Which Azure Blob Storage upload method is most suitable for handling large files while ensuring data integrity?
Develop for Azure storage
A.Put Blob
B.Append Blob
C.Page Blob
D.Put Block List
Show answerAnswer
D. Put Block List
Put Block List allows large files to be uploaded in smaller, manageable blocks. These blocks are then committed as a single blob, providing atomic writes and ensuring data integrity even if parts of the upload fail.
18. A developer is creating an application that processes orders. When an order is placed, a message needs to be sent to a backend processing service that might experience intermittent unavailability. The messages must be guaranteed to be delivered at least once, and the processing service should be able to retrieve messages in the order they were sent. Which Azure service should the developer use?
Develop for Azure storage
A.Azure Event Hubs
B.Azure Cache for Redis
C.Azure Service Bus
D.Azure Queue Storage
Show answerAnswer
C. Azure Service Bus
Azure Service Bus is a highly reliable message broker that supports advanced messaging patterns, including guaranteed at-least-once delivery and ordered message processing using sessions or FIFO queues. It's well-suited for scenarios where components might be temporarily offline.
19. A company is developing a new application that will store user-generated content, including photos and short videos. These files will be uploaded frequently and need to be immediately available for viewing by other users. The application also requires a robust mechanism for handling eventual consistency across multiple regions, ensuring data integrity even if a region becomes temporarily unavailable. Which Azure Blob Storage replication strategy best meets these requirements?
Develop for Azure storage
A.Locally Redundant Storage (LRS)
B.Zone-Redundant Storage (ZRS)
C.Geo-Redundant Storage (GRS)
D.Read-Access Geo-Redundant Storage (RA-GRS)
Show answerAnswer
D. Read-Access Geo-Redundant Storage (RA-GRS)
RA-GRS provides geo-redundancy (data replicated to a secondary region) and allows read access to the data in the secondary region. This ensures high availability and data integrity even if the primary region fails. While GRS also provides geo-redundancy, RA-GRS explicitly allows reads from the secondary, making it suitable for scenarios where data needs to be immediately viewable and eventually consistent across regions during failovers.
20. A web application stores user profile images in Azure Blob Storage. These images are frequently accessed for the first 30 days, then rarely accessed for the next 90 days, and finally almost never accessed but must be retained for compliance. To optimize costs, the company wants to automatically move blobs between tiers based on their access patterns. Which Azure Blob Storage feature should be implemented?
Develop for Azure storage
A.Immutable storage
B.Blob index tags
C.Lifecycle management policies
D.Soft delete
Show answerAnswer
C. Lifecycle management policies
Azure Blob Storage lifecycle management policies allow you to define rules to automatically transition blobs between access tiers (Hot, Cool, Archive) or delete them based on age, last modified time, or access time. This directly addresses the requirement for cost optimization by automating tier transitions.
21. A developer is building a mobile application that needs to store small amounts of structured data, such as user preferences and application settings. This data must be highly available and resilient, but does not require complex joins or relationships. The solution needs to be cost-effective for millions of entities with simple key-value lookups. Which Azure Storage solution is the most appropriate?
Develop for Azure storage
A.Azure Cosmos DB (Core API)
B.Azure Blob Storage
C.Azure SQL Database
D.Azure Table Storage
Show answerAnswer
D. Azure Table Storage
Azure Table Storage is a NoSQL key-value store optimized for large datasets of structured, non-relational data, offering high availability and cost-effectiveness for simple lookups, making it ideal for user preferences and application settings.
22. A developer is writing code to manage blobs in Azure Blob Storage. The application needs to retrieve a list of all JPEG images stored within a specific virtual folder (e.g., 'photos/2023/'). The solution should be efficient and avoid downloading unnecessary blob metadata. Which method should the developer use?
Develop for Azure storage
A.ListBlobs with a prefix 'photos/2023/' and include=BlobProperties to get content type.
B.ListBlobs with a prefix 'photos/2023/' and filter the results by checking the blob name ends with '.jpg'.
C.ListBlobs with a prefix 'photos/2023/' and a delimiter '/' to enumerate virtual directories.
D.ListBlobs with a prefix 'photos/2023/' and filter by file extension locally.
Show answerAnswer
B. ListBlobs with a prefix 'photos/2023/' and filter the results by checking the blob name ends with '.jpg'.
Using ListBlobs with a prefix 'photos/2023/' will efficiently retrieve only blobs within that virtual folder. Then, filtering the results by checking the blob name for '.jpg' will ensure only JPEG images are processed, without needing to download full blob properties or content.
23. A company stores customer order data in Azure Cosmos DB. Each order document contains a `customerId` and an `orderId`. The application frequently queries orders by a specific `customerId` and also needs to retrieve individual orders very quickly using both `customerId` and `orderId`. The development team needs to choose an optimal partitioning strategy to ensure low latency and cost-effective operations.
Develop for Azure storage
A.Partition by `/customerId`.
B.Partition by `orderId`.
C.Partition by `/orderId` and use `customerId` as a secondary index.
D.Partition by a composite key of `/customerId` and `/orderId`.
Show answerAnswer
A. Partition by `/customerId`.
Partitioning by `/customerId` is optimal for this scenario. It ensures that all orders for a single customer reside on the same logical partition, making queries by `customerId` efficient (single-partition queries). When retrieving individual orders by `customerId` and `orderId`, specifying `customerId` as the partition key in the query allows Cosmos DB to quickly locate the correct logical partition, then efficiently find the `orderId` within that partition.
24. A company is developing a new application that will process high volumes of telemetry data from IoT devices. The data is time-series in nature, requiring fast writes and efficient querying across time ranges and device IDs. The solution must support millions of data points per second and scale globally. Which Azure Cosmos DB API is the MOST appropriate for this scenario?
Develop for Azure storage
A.Gremlin API
B.SQL (Core) API
C.MongoDB API
D.Cassandra API
Show answerAnswer
D. Cassandra API
The Cassandra API is specifically optimized for high-throughput, time-series data, and is well-suited for IoT telemetry due to its distributed nature and efficient write/read patterns for this type of workload. Its column-family model aligns well with structured time-series data.
25. A manufacturing plant uses Azure Queue Storage to process messages from factory sensors. Each message contains telemetry data that needs to be processed by a backend service. Due to intermittent network issues, the backend service occasionally fails to process a message completely. The developer needs to ensure that a failed message is automatically returned to the queue for reprocessing after a short delay, without immediately being available to other consumers.
Develop for Azure storage
A.Increase the queue's maximum message size.
B.Configure the message's visibility timeout.
C.Implement a dead-letter queue for failed messages.
D.Set the message's TimeToLive property to a short duration.
Show answerAnswer
B. Configure the message's visibility timeout.
The visibility timeout in Azure Queue Storage specifies how long a message remains invisible to other consumers after it has been dequeued. If the consumer fails to process and delete the message within this timeout, the message becomes visible again and can be reprocessed, which meets the requirement for automatic reprocessing after a short delay.
Customer-managed keys (CMK) allow you to use your own encryption keys from Azure Key Vault to encrypt data at rest in Azure Storage, providing greater control over your encryption keys.
Keys are stored and managed in Azure Key Vault.
Provides enhanced control over encryption key lifecycle.
Applies to data at rest encryption for Azure Blob, File, Table, and Queue storage.
A feature of Azure Blob Storage that automatically saves the previous state of a blob each time it's modified or deleted, allowing recovery of earlier versions.
Azure Cosmos DB's global distribution capabilities allow data to be replicated across multiple Azure regions. For read-heavy workloads, deploying read replicas in regions geographically close to users significantly reduces read latency by serving data from the nearest replica.
Replicate data across any number of Azure regions.
Reads served from the closest replica for lowest latency.
Requires specifying preferred regions for client SDK.
Azure Cosmos DB's Core (SQL) API is a NoSQL document database designed for high-performance, globally distributed applications, capable of storing unstructured JSON data with flexible schemas, making it ideal for high-volume IoT telemetry.
Supports JSON documents with flexible schema.
Offers high throughput and low-latency access.
Provides robust SQL-like querying capabilities for JSON.
Strong consistency in Azure Cosmos DB guarantees that all reads return the most recent committed version of an item. This provides the highest level of data consistency across all replicas, at the cost of potentially higher latency and lower throughput compared to weaker models.
Azure Queue Storage is a service for storing large numbers of messages. You access messages from anywhere in the world via authenticated calls using HTTP or HTTPS. A queue message can be up to 64 KB in size, and a queue can contain millions of messages, up to the total capacity limit of a storage account.
When listing blobs in Azure Blob Storage, the `prefix` parameter allows you to filter the results to only include blobs whose names begin with the specified string, effectively simulating listing contents of a virtual directory.
Filters blobs server-side, improving efficiency.
Useful for querying 'virtual directories' in flat blob storage.
Can be combined with `delimiter` for hierarchical listing.
Bounded Staleness is an Azure Cosmos DB consistency level that guarantees that reads are always within a specified number of versions or a specified time interval of the latest writes. It provides a balance between strong consistency and eventual consistency, allowing for higher throughput and lower latency than Strong consistency.
Reads lag behind writes by at most 'K' versions or 'T' time interval.
Offers a balance between strong and eventual consistency.
Azure Cosmos DB is well-suited for IoT solutions due to its ability to handle high-volume, high-velocity data ingestion, flexible schema, and low-latency access.
The Azure Blob Storage Archive tier is an offline tier optimized for rarely accessed data that can tolerate several hours of retrieval latency, offering the lowest storage cost.
The Azure Cosmos DB Core (SQL) API is the native API for Cosmos DB, designed for JSON documents. It provides a flexible schema, low latency access, and a powerful SQL-like query language for querying data.
Block blobs are optimized for uploading large amounts of data efficiently. They allow files to be broken into smaller blocks, uploaded independently, and then committed as a single, complete blob, ensuring atomicity and integrity.
Ideal for large files (GBs to TBs).
Data uploaded in blocks (up to 50,000 blocks per blob).
Blocks are committed using `Put Block List` operation.
Azure Service Bus is a fully managed enterprise integration message broker. It can decouple applications and services, offering features like reliable asynchronous message delivery, message sessions for ordered processing, dead-lettering, and publish/subscribe capabilities.
Read-Access Geo-Redundant Storage (RA-GRS) replicates your data to a secondary region hundreds of miles away from the primary region. It provides read access to the data in the secondary region, allowing for high availability and disaster recovery, even if the primary region becomes unavailable.
Geo-redundant: data replicated to a secondary region.
Provides read access to data in the secondary region.
Offers eventual consistency for reads from the secondary.
Azure Table Storage is a NoSQL key-value store that allows for storing large amounts of structured, non-relational data. It's highly available, scalable, and cost-effective for scenarios requiring fast lookups on simple data models.
The `ListBlobs` operation in Azure Blob Storage allows specifying a prefix to filter the returned blobs, effectively listing blobs within a virtual directory.
Server-side filtering for efficiency.
Treats hierarchical data like folders.
Can be combined with delimiters for directory enumeration.
Choosing an effective partition key in Azure Cosmos DB is crucial for performance and cost. A good partition key distributes data evenly and supports frequent query patterns by allowing single-partition queries, where all relevant data for a query resides within one logical partition.
Distributes data across logical and physical partitions.
Impacts query performance and cost (single- vs. cross-partition).
Should have high cardinality and spread request units evenly.
The Azure Cosmos DB Cassandra API provides a highly scalable, globally distributed, and low-latency database service for Apache Cassandra applications.
Ideal for time-series, IoT, and archival data.
Supports Cassandra Query Language (CQL).
Offers high throughput and low latency for large datasets.
The visibility timeout in Azure Queue Storage determines how long a dequeued message remains invisible to other consumers. If the message is not deleted within this period, it becomes visible again for reprocessing.
Questions are original practice items written to match the published exam objectives. Step2Study is not affiliated with or endorsed by any certification body.