Microsoft Practice Questions, Discussions & Exam Topics by our Authors

DRAG DROP - You are developing a web service that will run on Azure virtual machines that use Azure Storage. You configure all virtual machines to use managed identities. You have the following requirements: * Secret-based authentication mechanisms are not permitted for accessing an Azure Storage account. * Must use only Azure Instance Metadata Service endpoints. You need to write code to retrieve an access token to access Azure Storage. To answer, drag the appropriate code segments to t...

Author: SolarFalcon11 · Last updated Jul 23, 2026

DRAG DROP - You are developing a new page for a website that uses Azure Cosmos DB for data storage. The feature uses documents that have the following format: You must display data for the new page in a specific order. You create the following query for the page: You need to configure a Cosmos DB policy to support the query. How should you configure the policy? To answer, drag the appropriate JSON segments to the correct locations. Each JSON segm...

Author: Michael · Last updated Jul 23, 2026

SNAPSHOT - You are building a traffic monitoring system that monitors traffic along six highways. The system produces time series analysis-based reports for each highway. Data from traffic sensors are stored in Azure Event Hub. Traffic data is consumed by four departments. Each department has an Azure Web App that displays the time series-based reports and contains a WebJob that processes the incoming data from Event Hub. All Web Apps run on App Service Plans with three instances. Data throughput must be maximized. ...

Author: Rahul · Last updated Jul 23, 2026

DRAG DROP - You are developing a microservices solution. You plan to deploy the solution to a multinode Azure Kubernetes Service (AKS) cluster. You need to deploy a solution that includes the following features: * reverse proxy capabilities * configurable traffic routing * TLS termination with a custom certificate Which components should you use? To answer, drag the appropriate components to the correct requirements. Each component ...

Author: Harper · Last updated Jul 23, 2026

DRAG DROP - You are implementing an order processing system. A point of sale application publishes orders to topics in an Azure Service Bus queue. The Label property for the topic includes the following data: The system has the following requirements for subscriptions: You need to implement filtering and maximize throughput while evaluating filters. Which filter types should you implement? To answer, drag the appropriate filter types to the correct subscriptions. Each...

Author: Nia · Last updated Jul 23, 2026

DRAG DROP - Your company has several websites that use a company logo image. You use Azure Content Delivery Network (CDN) to store the static image. You need to determine the correct process of how the CDN and the Point of Presence (POP) server will distribute the image and list the items in the correct order. In which order do the...

Author: Aarav · Last updated Jul 23, 2026

You are developing an Azure Cosmos DB solution by using the Azure Cosmos DB SQL API. The data includes millions of documents. Each document may contain hundreds of properties. The properties of the documents do not contain distinct values for partitioning. Azure Cosmos DB must scale individual containers in the database to meet the performance needs of the application by spreading the workload evenly across all partitions ov...

To choose the correct partition key for an Azure Cosmos DB solution, it’s essential to understand the requirement of distributing data evenly across partitions while ensuring scalability and performance. Let's examine the options and explain why they are appropriate or not. Explanation of Each Option: 1. A) A single property value that does not appear frequently in the documents - Rejected: Using a partition key that has values that don't appear frequently is not ideal. Azure Cosmos DB distributes data across partitions based on the partition key. If the chosen property does not have many distinct values (or is rarely present in documents), this could lead to hot partitioning, where a few partitions receive most of the load, and others remain underutilized. This would result in poor performance and lack of scalability. 2. B) A value containing the collection name - Rejected: The collection name is the same for all documents within a given container and does not provide any meaningful partitioning of the data. Since all documents in a container share the same collection name, using this as a partition key would effectively place all documents in a single partition, severely limiting the scalability and performance of the Cosmos DB container. 3. C) A single property value that appears frequently in the documents - Rejected: A property value that appears frequently in documents can cause uneven distribution of data across partitions. If one value is heavily repeated, it could lead to a hot partition, where one partition stores a disproportionate amount of data, limiting scalability. This will result in performance bottlenecks because the hot partition becomes a performance bottlen...

Author: Rohan · Last updated Jul 23, 2026

SNAPSHOT - You are developing an Azure-hosted e-commerce web application. The application will use Azure Cosmos DB to store sales orders. You are using the latest SDK to manage the sales orders in the database. You create a new Azure Cosmos DB instance. You include a valid endpoint and valid authorization key to an appSettings.json file in the code project. You are evaluating the following application code: (Line number are inc...

Author: Emily · Last updated Jul 23, 2026

DRAG DROP - You develop an Azure solution that uses Cosmos DB. The current Cosmos DB container must be replicated and must use a partition key that is optimized for queries. You need to implement a change feed processor solution. Which change feed processor components should you use? To answer, drag the appropriate components to the correct requirements. Each component may be used once, more th...

Author: Leah · Last updated Jul 23, 2026

SNAPSHOT - You are developing a web application that will use Azure Storage. Older data will be less frequently used than more recent data. You need to configure data storage for the application. You have the following requirements: * Retain copies of data for five years. * Minimize costs associated with storing data that is over one year old. * Implement Zone Redundant Stora...

Author: VenomousSerpent42 · Last updated Jul 23, 2026

SNAPSHOT - A company develops a series of mobile games. All games use a single leaderboard service. You have the following requirements: * Code must be scalable and allow for growth. * Each record must consist of a playerId, gameId, score, and time played. * When users reach a new high score, the system will save the new score using the SaveScore function below. Each game is assigned an Id based on the series title. You plan to store customer information in Azure Cosmos DB. The following data already exists in the database: You develop the following code to save scores in the data store. (Line numbers are included for refe...

Author: Kunal · Last updated Jul 23, 2026

You develop and deploy a web application to Azure App Service. The application accesses data stored in an Azure Storage account. The account contains several containers with several blobs with large amounts of data. You deploy all Azure resources to a single region. You need t...

To move an Azure Storage account to a new region and copy all data, the first thing you need to do is ensure that the data is copied to the new region. Let's go through the available options and explain the reasoning behind the correct choice. Explanation of Each Option: 1. A) Export the Azure Storage account Azure Resource Manager (ARM) template - Rejected: Exporting an ARM template generates a template that can be used to deploy the storage account configuration (such as properties, settings, and resources) but does not handle data movement. This option would only help in replicating the configuration but not the actual data. It does not address copying the large amounts of data stored in blobs to the new region, so this is not suitable for your needs. 2. B) Initiate a storage account failover - Rejected: A failover in Azure Storage accounts is a mechanism used to switch from a primary region to a secondary region within the same geo-redundant storage configuration (e.g., GRS or RA-GRS). This is meant for disaster recovery scenarios where the primary region becomes unavailable. It does not help in moving a storage account to a new region. Initiating a failover will only affect the availability region but not move or copy the data to a new region. 3. C) Configure object replication for all blobs - Rejected: Object replication (Azure Storage replication) refers to replicating data between containers in different storage accounts within the same region or across regions. While this option could be used to replicate data to another region, it requires careful setup and would only replicate new writes after configuration is complete. However, this option is not the first step in moving data because it does not automatically copy all the existing blobs in the storage account and would be more of an ongoing replication solution once set up. 4. D) Use the AzCopy command line tool - Selected Option: ...

Author: StarryEagle42 · Last updated Jul 23, 2026

SNAPSHOT - You are developing an application to collect the following telemetry data for delivery drivers: first name, last name, package count, item id, and current location coordinates. The app will store the data in Azure Cosmos DB. You need to configure Azure Cosmos DB to query the data. Which values sho...

Author: Emma · Last updated Jul 23, 2026

DRAG DROP - You are implementing an Azure solution that uses Azure Cosmos DB and the latest Azure Cosmos DB SDK. You add a change feed processor to a new container instance. You attempt to read a batch of 100 documents. The process fails when reading one of the documents. The solution must monitor the progress of the change feed processor instance on the new container as the change feed is read. You must prevent the change feed processor from retrying the entire batch when one document cannot be read. You need to implement the change feed processor to read the documents. Which features should you use? To ans...

Author: Aria · Last updated Jul 23, 2026

SNAPSHOT - You are developing an application that uses a premium block blob storage account. The application will process a large volume of transactions daily. You enable Blob storage versioning. You are optimizing costs by automating Azure Blob Storage access tiers. You apply the following policy rules to the storage account. (Line numbers are included for reference only....

Author: Ava · Last updated Jul 23, 2026

An organization deploys Azure Cosmos DB. You need to ensure that the index is updated as items are creat...

To ensure that the index is updated as items are created, updated, or deleted in Azure Cosmos DB, it's crucial to configure the indexing behavior correctly. Let's analyze each of the options to understand which one best fits the requirement. Explanation of Each Option: 1. A) Set the indexing mode to Lazy - Rejected: The Lazy indexing mode does not immediately index data when it is written to the database. Instead, it performs the indexing asynchronously, which may lead to situations where the index is not immediately updated after item creation, update, or deletion. This can cause delays in query results until the indexing process completes. Therefore, this option does not meet the requirement of ensuring that the index is updated in real-time when items are modified. 2. B) Set the value of the automatic property of the indexing policy to False - Rejected: The automatic property in the indexing policy determines whether indexing is enabled by default for all properties of documents. If set to False, indexing is turned off for properties, which means that items will not be indexed automatically, and the database will not update the index when items are created, updated, or deleted. This would prevent any indexing at all, making it...

Author: MysticJaguar44 · Last updated Jul 23, 2026

You are developing a .Net web application that stores data in Azure Cosmos DB. The application must use the Core API and allow millions of reads and writes. The Azure Cosmos DB account has been created with multiple write regions enabled. The application has been deployed to the East US2 and Central US regions. You need to update the application to support multi-regio...

To enable multi-region writes for your Azure Cosmos DB setup, we need to ensure that the application can interact with multiple write regions effectively, especially when the application is deployed to multiple regions (East US2 and Central US in this case). Let's go through each option to see which two solutions are valid for achieving this. Explanation of Each Option: 1. A) Update the ConnectionPolicy class for the Cosmos client and populate the PreferredLocations property based on the geo-proximity of the application. - Rejected: The PreferredLocations property helps Cosmos DB clients prioritize read operations from the nearest region to the client, but it does not enable multi-region writes. While this property can enhance read performance by choosing the closest read region, it doesn’t address the need to configure multiple write regions. Multi-region writes require a different setting in the Cosmos DB configuration, which is not achieved by this option. 2. B) Update Azure Cosmos DB to use the Strong consistency level. Add indexed properties to the container to indicate region. - Rejected: The Strong consistency level guarantees consistency across regions but is not necessary for enabling multi-region writes. Multi-region writes can be used with consistency levels such as Eventual or Session, so this solution doesn’t align with the goal of enabling multi-region writes. Also, indexed properties to indicate region do not affect the ability to perform multi-region writes, so this is not a valid approach for enabling the desired functionality. 3. C) Update the ConnectionPolicy class for the Cosmos client and set the UseMultipleWriteLocations property to true. - Selected Option: Setting UseMultipleWriteLocations to `true` in the ConnectionPolicy class allows your application to write to multiple regions. This is the correct configuration for enabling multi-region writes in Cosmos DB. When enabled, writes ...

Author: Krishna · Last updated Jul 23, 2026

SNAPSHOT - You are developing a solution to store documents in Azure Blob storage. Customers upload documents to multiple containers. Documents consist of PDF, CSV, Microsoft Office format and plain text files. The solution must process millions of documents across hundreds of containers. The solution must meet the following requirements: * Documents must be categorized by a customer identifier as they are uploaded to the storage account. * Allow filtering by the customer identifier. * Allow searching of information contained within a document * Minimize costs. You create and configu...

Author: Isabella1 · Last updated Jul 23, 2026

SNAPSHOT - You are developing a web application by using the Azure SDK. The web application accesses data in a zone-redundant BlockBlobStorage storage account. The application must determine whether the data has changed since the application last read the data. Update operations must use the latest data changes when writing data to the storage account. You need to implement the upd...

Author: John · Last updated Jul 23, 2026

SNAPSHOT - An organization deploys a blob storage account. Users take multiple snapshots of the blob storage account over time. You need to delete all snapshots of the blob storage account. You must not delete the blob storage account itself. How should you complete the code segment?...

Author: NebulaEagle11 · Last updated Jul 23, 2026

SNAPSHOT - An organization deploys a blob storage account. Users take multiple snapshots of the blob storage account over time. You need to delete all snapshots of the blob storage account. You must not delete the blob storage account itself. How should you complete the code segment?...

Author: Ella · Last updated Jul 23, 2026

SNAPSHOT - You are developing an application that monitors data added to an Azure Blob storage account. You need to process each change made to the storage account. How should you complete the code segment? To answer, se...

Author: Zara · Last updated Jul 23, 2026

SNAPSHOT - You develop an application that sells AI generated images based on user input. You recently started a marketing campaign that displays unique ads every second day. Sales data is stored in Azure Cosmos DB with the date of each sale being stored in a property named =E2=80=98whenFinished'. The marketing department requires a view that shows the number of sales for each unique ad. You need to imple...

Author: Jack · Last updated Jul 23, 2026

SNAPSHOT - You implement an Azure solution to include Azure Cosmos DB, the latest Azure Cosmos DB SDK, and the Core (SQL) API. You also implement a change feed processor on a new container instance by using the Azure Functions trigger for Azure Cosmos DB. A large batch of documents continues to fail when reading one of the documents in the batch. The same batch of documents is continuously retried by the triggered function and a new batch of documents must be read. You need to ...

Author: Layla · Last updated Jul 23, 2026

You are developing an application to store business-critical data in Azure Blob storage. The application must meet the following requirements: * Data must not be modified or deleted for a user-specified interval. * Data must be protected from overwrites and deletes. * Data must be written once and allowed to be read many times. You need to protect the data in the Azure ...

To protect business-critical data in Azure Blob Storage with the specified requirements, we need to ensure the data cannot be modified, deleted, or overwritten for a user-specified interval. Let's examine the options to identify which ones can achieve this and why others are not suitable. Explanation of Each Option: 1. A) Configure a time-based retention policy for the storage account. - Selected Option: A time-based retention policy allows you to define a period during which data cannot be deleted or modified. This aligns perfectly with the requirement of ensuring that data is protected from deletion or modification for a user-specified interval. When this policy is applied, it prevents any operation that would alter or delete data, making it ideal for meeting the "data must not be modified or deleted" requirement. 2. B) Create an account shared-access signature (SAS). - Rejected: An account-level SAS grants permissions to specific resources, but it does not inherently protect data from modification or deletion. It is mainly used to allow secure access to resources over a specified period. However, it doesn't provide the necessary immutability features required to prevent data from being modified or deleted, as it can still allow delete or overwrite actions based on the permissions set in the SAS token. Therefore, this option doesn't meet the requirement. 3. C) Enable the blob change feed for the storage account. - Rejected: The blob change feed is useful for tracking changes in blobs, such as modifications, uploads, and deletions. However, it does not prevent data from being modified or deleted; it only logs changes. This does not align with the requirement to protect the data from modification or deletion. Therefore, this option is not a solution to protect the data. 4. D) Enable version-level immutability support for the storage ...

Author: Ahmed · Last updated Jul 23, 2026

You are updating an application that stores data on Azure and uses Azure Cosmos DB for storage. The application stores data in multiple documents associated with a single username. The application requires the ability to update multiple documents for a username in a single ACID operation. You need to configure Azure Cosmos DB....

To update multiple documents in a single ACID operation in Azure Cosmos DB, it’s important to understand how transactions and ACID operations work in Cosmos DB, as well as the need for handling multiple documents that are associated with a specific username. Let’s analyze the provided options to see which ones would allow multiple document updates for the same username within an ACID transaction. Explanation of Each Option: 1. A) Create a collection sharded on username to store documents. - Rejected: Sharding on the username can help distribute data across partitions based on the username, but sharding itself does not guarantee ACID transactions across multiple documents. Sharding in Cosmos DB (via partitioning) helps in distributing data for scalability, but ACID transactions are only supported within a single partition. If the documents are sharded across multiple partitions, there would be no guarantee of a transactional update across those partitions. Therefore, this option alone does not provide ACID support for multiple documents associated with the same username. 2. B) Configure Azure Cosmos DB to use the Gremlin API. - Rejected: The Gremlin API in Cosmos DB is designed for graph-based data models, which are optimized for graph traversal operations (such as querying relationships between nodes). It’s not optimized for document updates or ACID transactions in the way needed for document-based scenarios like the one described in the question. Therefore, the Gremlin API is not the appropriate choice for this requirement. 3. C) Create an unsha...

Author: Nathan · Last updated Jul 23, 2026

You develop Azure solutions. You must connect to a No-SQL globally-distributed database by using the .NET API. You need to create an object to configure and ...

To connect to a No-SQL globally distributed database like Azure Cosmos DB using the .NET API, you need to configure a CosmosClient object to establish the connection, then create a database or container as needed, and execute requests against it. Let's analyze each option to determine which is correct and why others are rejected: Explanation of Each Option: 1. A) database_name = 'MyDatabase' database = client.create_database_if_not_exists(id=database_name) - Rejected: This code appears to be written in Python syntax (not .NET). The `.NET API` would require the use of `CosmosClient` and proper .NET method calls. The syntax used in this example (`database_name = 'MyDatabase'`) is not valid for a .NET environment, and thus, this option is not appropriate for the question. 2. B) client = CosmosClient(endpoint, key) - Selected Option: This code is correct for initializing a CosmosClient in .NET. The CosmosClient is the key object in the Azure Cosmos DB .NET SDK for interacting with the database. The client is configured using the endpoint (the URI of your Cosmos DB account) and the key (the authorization key for accessing the database). Once the client is instantiated, y...

Author: Akash · Last updated Jul 23, 2026

You develop a web application that provides access to legal documents that are stored on Azure Blob Storage with version-level immutability policies. Documents are protected with both time-based policies and legal hold policies. All time-based retention policies have the AllowProtectedAppendWrites property enabled. You have a requirement to prevent the user from attempting to perform operations that would fail only when a legal hold is in effect and when all other p...

To meet the requirement of preventing the user from performing operations that would fail only when a legal hold is in effect and when all other time-based retention policies have expired, we need to understand how these policies function: - Legal hold: When a legal hold is applied to a document, it prevents any modifications, deletions, or overwrites of that document until the hold is released. - Time-based retention policies: These policies protect data for a specified retention period. After the period expires, operations like delete and overwrite are allowed, unless restricted by a legal hold or other active protection. - AllowProtectedAppendWrites: This property allows appending data to a document even if a retention policy is in place, but it still does not allow overwriting or deleting the document. Explanation of Each Option: 1. A) Adding data to documents - Rejected: The AllowProtectedAppendWrites property enables appending data to the document even if time-based retention policies are in place. This operation is allowed under the time-based retention policies, and the legal hold does not restrict this. Therefore, adding data to documents is not something we need to prevent. 2. B) Deleting documents - Selected Option: Deleting documents is restricted by both legal hold policies and time-based retention policies. While time-ba...

Author: Ryan · Last updated Jul 23, 2026

SNAPSHOT - You provisioned an Azure Cosmos DB for NoSQL account named account1 with the default consistency level. You plan to configure the consistency level on a per request basis. The level needs to be set for consistent prefix for read and write operations to account1. You need to identify the resulting consistency level for read and write operati...

Author: Oscar · Last updated Jul 23, 2026

DRAG DROP - You are developing an application to store millions of images in Azure blob storage. The images are uploaded to an Azure blob storage container named companyimages contained in an Azure blob storage account named companymedia. The stored images are uploaded with multiple blob index tags across multiple blobs in the container. You must find all blobs whose tags match a search expression in the container. The search expression must evaluate an index tag named status with a value of final. You need to construct the GET method request URI. How s...

Author: Madison · Last updated Jul 23, 2026

SNAPSHOT - You develop two Python scripts to process data. The Python scripts must be deployed to two, separate Linux containers running in an Azure Container Instance container group. The containers must access external data by using the Server Message Block (SMB) protocol. Containers in the container group must run only once. You need to configure the Azure Container Ins...

Author: Ava · Last updated Jul 23, 2026

SNAPSHOT - You are developing a static website hosted on Azure Blob Storage. You create a storage account and enable static website hosting. The website must support the following requirements: * Custom domain name * Custom header values for all responses * Custom SSL certificate You need to implement the static website...

Author: Alexander · Last updated Jul 23, 2026

You are developing an inventory tracking solution. The solution includes an Azure Function app containing multiple functions triggered by Azure Cosmos DB. You plan to deploy the solution to multiple Azure regions. The solution must meet the following requirements: * Item results from Azure Cosmos DS must return the most recent committed version of an item. * Items written to Azure C...

To meet the requirements for your inventory tracking solution that includes multiple Azure regions and ensures that item results from Azure Cosmos DB return the most recent committed version of an item, and that items written to Cosmos DB provide ordering guarantees, you must select an appropriate consistency level for your Azure Cosmos DB deployments. Let’s analyze each of the consistency levels to determine which meets the criteria. Explanation of Each Option: 1. A) Consistent Prefix - Rejected: The Consistent Prefix consistency level ensures that reads always return data in the order they were written, and prevents reading out-of-order updates (e.g., you cannot read a newer version of a document before an older version). However, it doesn't guarantee that you always get the most recent committed version of an item, as it allows eventual consistency. This may not satisfy the requirement to always return the most recent committed version of an item. 2. B) Eventual - Rejected: The Eventual consistency level offers the least strict guarantees. It allows the system to eventually converge to the correct state but doesn't guarantee the order of reads and writes. This does not meet the requirement of ordering guarantees or ensuring the most recent committed version of an item is returned. As a result, it is not appropriate for scenarios where you need the most up-to-date data and ordering guarantees. 3. C) Bounded Staleness - Rejected: The Bounded Staleness consistency level provides a configurable delay between reads...

Author: Zara · Last updated Jul 23, 2026

SNAPSHOT - You are developing an application that runs in several customer Azure Kubernetes Service clusters. Within each cluster, a pod runs that collects performance data to be analyzed later. A large amount of data is collected so saving latency must be minimized. The performance data must be stored so that pod restarts do not impact the stored data. Write latency should be minimized. You need to configu...

Author: Noah Williams · Last updated Jul 23, 2026

SNAPSHOT - Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - V...

Author: Ethan Smith · Last updated Jul 23, 2026

You create and publish a new Azure App Service web app. User authentication and authorization must use Azure Active Directory (Azure AD). You need to con...

To configure authentication and authorization for an Azure App Service web app using Azure Active Directory (Azure AD), the first step is to enable Azure AD authentication and set up the necessary configurations. Let’s break down the options and determine which one is the correct first step. Explanation of Each Option: 1. A) Add an identity provider - Selected Option: This is the correct first step. To integrate Azure AD authentication with an Azure App Service web app, you need to add Azure AD as an identity provider in the App Service Authentication settings. This enables the app to authenticate users using Azure AD and also handle authorization based on Azure AD roles and permissions. Once this is done, users can log in with their Azure AD credentials. - Adding Azure AD as the identity provider establishes the connection between your app and the Azure AD tenant, which is necessary for user authentication and authorization. 2. B) Map an existing custom DNS name - Rejected: While mapping a custom DNS name to your app is a useful configuration for providing your app with a branded URL (e.g., `www.yourapp.com`), it is not related to configuring authentication or authorization. Mapping a custom domain is typically done after setting up authentication and ensuring the application is working properly. 3. C) Create and configure a new app setting - Rejected: App settings are typically used for configuring application-specific settings (like database connection strings, keys, or environment-spe...

Author: Kunal · Last updated Jul 23, 2026

DRAG DROP - You have an Azure Cosmos DB for NoSQL account. You plan to develop two apps named App1 and App2 that will use the change feed functionality to track changes to containers. App1 will use the pull model and App2 will use the push model. You need to choose the method to track the most recently processed change in App1 and App2. Which component should you use? To answer, drag the appropriate components to the correct apps....

Author: John · Last updated Jul 23, 2026

You have a Linux container-based console application that uploads image files from customer sites all over the world. A back-end system that runs on Azure virtual machines processes the images by using the Azure Blobs API. You are not permitted to make changes to the application. Some customer sites only...

In this scenario, you're working with a Linux container-based console application that uploads image files from customer sites across the world. Since some customer sites only have phone-based internet connections, the solution must efficiently access and upload images while dealing with potential limitations in bandwidth. Let's review the options provided: Explanation of Each Option: 1. A) Azure BlobFuse - Selected Option: Azure BlobFuse is a virtual file system driver that allows you to mount an Azure Blob Storage container as a local directory on a Linux machine. It provides a way to access Azure Blob Storage in a more native way, as if it's a filesystem. Given the scenario, BlobFuse is a good choice because it allows the application to access Azure Blob Storage without needing to make significant changes to the application itself. It provides a seamless interface for accessing image files directly from Blob Storage using standard Linux file system operations. - Key Benefit: BlobFuse is particularly useful when working with applications that require file-based access to Blob Storage and do not need to make changes to the application itself. It can handle low-bandwidth scenarios like phone-based internet connections by efficiently interacting with Azure Blob Storage, avoiding complex protocols and reducing the need for heavy data manipulation. 2. B) Azure Disks - Rejected: Azure Disks are block-level storage that are typically used for virtual machine disks (OS or data disks). They are not intended for direct application-level access or for use with containerized applications. Moreove...

Author: Harper · Last updated Jul 23, 2026

DRAG DROP - You are developing several microservices named serviceA, serviceB, and serviceC. You deploy the microservices to a new Azure Container Apps environment. You have the following requirements: * The microservices must persist data to storage. * serviceA must persist data only visible to the current container and the storage must be restricted to the amount of disk space available in the container. * serviceB must persist data for the lifetime of the replica and allow multiple containers in the replica to mount the same storage location. * serviceC must persist data beyond the lifetime of the replica while allowing multiple containers to access the storage and enable per object permissions. You need to configure storage for e...

Author: Stella · Last updated Jul 23, 2026

DRAG DROP - You are developing a web service that will run on Azure virtual machines that use Azure Storage. You configure all virtual machines to use managed identities. You have the following requirements: * Secret-based authentication mechanisms are not permitted for accessing an Azure Storage account. * Must use only Azure Instance Metadata Service endpoints. You need to write code to retrieve an access token to access Azure Storage. To answer, drag the appropriate code ...

Author: Vikram · Last updated Jul 23, 2026

SNAPSHOT - You are developing an Azure Function app. The Azure Function app must enable a WebHook to read an image from Azure Blob Storage and create a new Azure Cosmos DB document. You need to implement the Azure Function app. Which configuration should you u...

Author: Kunal · Last updated Jul 23, 2026

You create an Azure Cosmos DB for NoSQL database. You plan to use the Azure Cosmos DB .NET SDK v3 API for NoSQL to upload the following files: You receive the following error message when uploading the files: '413 Entity too large'. You need to...

Author: Emma · Last updated Jul 23, 2026

You are developing an app to store globally distributed data in several Azure Blob Storage containers. Each container hosts multiple blobs where each instance of the app will store the data. You enable versioning and soft delete for the blobs. App testing and incorrect code have frequently corrupted data. Development of the app must allow dat...

In this scenario, you need to restore data to a previous point in time for testing purposes and support the development process while using Azure Blob Storage. The app uses versioning and soft delete, but the critical requirement is to be able to restore data to a specific day for testing when data is corrupted. Let's analyze the options and determine the best one. Explanation of Each Option: 1. A) Enable the change feed on the storage account to begin capturing and recording changes - Selected Option: Enabling the change feed on the storage account is the best choice to meet the requirement for point-in-time restore. The Azure Blob Storage change feed provides a chronological log of all operations that modify or delete blobs in the storage account. By using the change feed, you can track changes and restore blobs to a specific point in time by replaying the operations up to the desired date. - Why Selected: This is specifically designed for tracking changes and enabling point-in-time restores by allowing you to go back and replay actions on blobs. The change feed provides a complete audit trail, making it easy to restore data to a known state before corruption or erroneous changes occurred. 2. B) Configure object replication and specify replication rules - Rejected: Object replication helps replicate data across regions for disaster recovery and high availability. However, it does not directly support point-in-time restoration of blobs. It is not designed to track specific changes or versions of the blobs, but instead ensures ...

Author: Zara · Last updated Jul 23, 2026

A company uses an Azure Blob Storage for archiving. The company requires that data in the Blob Storage is only in the archive tier. You need to ensure data copied...

Let's analyze each option and explain why it might or might not be appropriate for this scenario, where the company requires that data in the Azure Blob Storage is only in the Archive tier: Option A: Use a Put Block List operation with a request header of x-ms-immutability-policy-mode - Explanation: The `x-ms-immutability-policy-mode` header is used to enforce retention policies on data by making it immutable, meaning no one can delete or modify the data until the retention period expires. However, this doesn't move the data to the Archive tier. The focus here is on data protection rather than tiering. - Rejection Reason: This option does not address the requirement to move data to the Archive tier; it is more about enforcing immutability for compliance purposes. - Scenario Use: This would be used when you need to prevent the deletion or modification of data (e.g., for regulatory reasons), but not for archiving. Option B: Create a lifecycle policy with an action of tierToArchive and configure daysAfterModificationGreaterThan for 0 - Explanation: A lifecycle policy can automate actions like moving blobs to different access tiers based on specific criteria. The `tierToArchive` action moves blobs to the Archive tier after the specified condition is met. Configuring `daysAfterModificationGreaterThan` for 0 ensures that blobs are moved to the Archive tier as soon as they are created or modified. - Selected Option Justification: This option directly satisfies the requirement to move data to the Archive tier. It automates the process by applying the tiering policy based on modification times, which fits the company’s needs of ensuring that all data in the Blob Storage is moved to the Archive tier. - Scenario Use: This option is perfect when you need automatic data tiering based on the age or modification time of the blobs, particularly when no other tiering conditions are involved. ...

Author: FrozenWolf2022 · Last updated Jul 23, 2026

SNAPSHOT - You have the following data lifecycle management policy: You plan to implement an Azure Blob Storage account and apply to it Policy1. The solution should maximize resiliency and performance. You need to configure the account to support the policy. Which redundancy option and storage accou...

Author: Daniel · Last updated Jul 23, 2026

SNAPSHOT - You have an Azure Cosmos DB for NoSQL API account named account1. Multiple instances of an on-premises application named app1 read data from account1. You plan to implement integrated cache for connections from the instances of app to account1. You need to set the connection mode and maximum consistency level of app1. Which values shou...

Author: Aria · Last updated Jul 23, 2026

You are developing a Cosmos DB solution that will be deployed to multiple Azure regions. Your solution must meet the following requirements: * Read operations will never receive write operations that are out of order. * Maximize concurrency of read operations in ...

Let's break down each consistency level option and evaluate which one best meets the requirements of ensuring no out-of-order writes during read operations and maximizing read concurrency across multiple regions in a Cosmos DB solution. Option A: Session - Explanation: The Session consistency level ensures that reads within a single session (i.e., the same client or request) are consistent with respect to the writes made during that session. It allows for high read and write availability within a session but doesn’t guarantee consistency between sessions. This consistency level is primarily useful for scenarios where each client requires a consistent view of their own data but does not care about other clients’ view of data. - Rejection Reason: This consistency level does not ensure global consistency (across regions) and could allow reads to receive stale data or out-of-order writes in a multi-region setup, which violates the first requirement. Also, it may not maximize concurrency across all regions. - Scenario Use: This would be useful if you wanted to ensure consistency for a single user's session but not across multiple regions or clients. Option B: Eventual - Explanation: The Eventual consistency level provides the highest availability and lowest latency. It ensures that updates to a Cosmos DB are propagated to all regions eventually, but there is no guarantee about when the data will become consistent across regions. Reads can potentially receive stale or out-of-order data during periods of replication delay. - Rejection Reason: This option fails to meet the requirement that read operations will never receive write operations that are out of order. Eventual consistency allows for out-of-order reads, meaning that it does not ensure global consistency or prevent reading inconsistent data. - Scenario Use: This is suitable for scenarios where availability and performance are prioritized over consistency, such as for non-critical applications where data accuracy can tolerate some delays. Option C: Bounded Staleness - Explanation: Bounded Staleness allows for a defined lag between when data is written and when it becomes available for reads in other regions. It guaran...

Author: VenomousSerpent42 · Last updated Jul 23, 2026

You have an Azure Queue Storage named queue1. You plan to develop code that will process messages in queue1. You need to implement a queue operation to set the visibility timeout value of individual messages in queue1. Which two operations can y...

Let's break down each option and determine which ones can be used to set the visibility timeout value of individual messages in Azure Queue Storage. Option A: Peek at a message in the queue - Explanation: Peek allows you to retrieve a message from the queue without changing its visibility or state. It doesn't affect the message in the queue at all, and the message remains visible to other consumers. - Rejection Reason: The Peek operation does not allow you to modify the visibility timeout or perform any updates to the message. Therefore, it does not meet the requirement to set the visibility timeout. - Scenario Use: This would be used when you want to examine a message without removing it or altering its state, but it cannot be used for visibility timeout modifications. Option B: Delete a message in the queue - Explanation: Delete removes a message from the queue permanently after it has been processed. The visibility timeout is not directly involved in the delete operation itself. - Rejection Reason: The Delete operation removes a message and does not allow for the modification of the visibility timeout of a message that is still in the queue. Therefore, it cannot be used to set the visibility timeout. - Scenario Use: This operation is useful for finalizing message processing by removing it from the queue, but it doesn't affect visibility timeouts. Option C: Add a message to the queue - Explanation: Add inserts a new message into the queue. While you can specify a visibility timeout when adding a message, this operation is used for adding new messages, not modifying existing ones. - Rejection Reason: This operation is used for adding messages to the queue and does not allow you to modify the visibility timeout of messages already in the queue. - Scenario Use: Useful when you need to enqueue a new message, but it does not support modifying existing messages' visib...

Author: Julian · Last updated Jul 23, 2026

SNAPSHOT - Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - F...

Author: Sofia · Last updated Jul 23, 2026

SNAPSHOT - A company has an Azure Cosmos DB for NoSQL account. The account is configured for session consistency. Data is written to a single Azure region and data can be read from three Azure regions. An application that will access the Azure Cosmos DB for NoSQL container data using an SDK has the following requirements: * Reads from the application must return the most recent committed version of an item from any Azure region. * The container items should not automatically be deleted....

Author: Emma Brown · Last updated Jul 23, 2026