Microsoft Practice Questions, Discussions & Exam Topics by our Authors

DRAG DROP - You are developing an Azure Function app. The app must meet the following requirements: * Enable developers to write the functions by using the Rust language. * Declaratively connect to an Azure Blob Storage account. You need to implement the app. Which Azure Function app features should you use? To answer, drag the appropriate features to the correct requirements. Each feature may be used on...

Author: Ava · Last updated Jul 23, 2026

SNAPSHOT - You are developing an ASP.NET Core web application. You plan to deploy the application to Azure Web App for Containers. The application needs to store runtime diagnostic data that must be persisted across application restarts. You have the following code: You need to configure the application settings so that diagnostic data is stored as required. How shoul...

Author: CrystalWolfX · Last updated Jul 23, 2026

You are developing a web app that is protected by Azure Web Application Firewall (WAF). All traffic to the web app is routed through an Azure Application Gateway instance that is used by multiple web apps. The web app address is contoso.azurewebsites.net. All traffic must be secured with SSL. The Azure Application Gateway instance is used by multiple web apps. You need to configure the Azure App...

To secure the web app and configure the Azure Application Gateway correctly, we need to ensure proper SSL encryption and routing. Let's evaluate the options one by one: Key Requirements: - SSL Encryption: All traffic must be secured with SSL. - Azure Application Gateway: This is used by multiple web apps, and the traffic must be routed correctly. - Azure Web Application Firewall (WAF): The traffic is routed through WAF, so we need to ensure the app’s traffic is properly managed. Option A: In the Azure Application Gateway's HTTP setting, enable the Use for App service setting. - Explanation: The "Use for App service" setting ensures that the Azure Application Gateway properly integrates with App Services (Web Apps), such as routing traffic securely and allowing SSL termination. By enabling this, you ensure that the gateway understands that traffic should be routed to an App Service, and it allows the app to be properly secured. - Why selected: This is a necessary step to ensure that the Azure Application Gateway is configured to work with Azure Web Apps. It enables SSL and routing compatibility. Option B: Convert the web app to run in an Azure App Service Environment (ASE). - Explanation: Azure App Service Environments (ASE) provide enhanced network isolation and support for custom domains and SSL certificates, but it is not required for configuring SSL or routing in a typical App Service. It is not a necessary step for securing traffic routed through an Azure Application Gateway. - Why rejected: This step is not mandatory for SSL encryption or for routing traffic through the Azure Application Gateway. It adds unnecessary complexity and is typically only used when enhanced isolation is required, which is not mentioned in the scenario. Option C: Add an authentication certificate for contoso.azurewebsites.net to the Azure Application Gateway. - Explanation: SSL certificates are used to ensure en...

Author: Sara · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You develop a software as a service (SaaS) offering to manage photographs. Users upload photos to a web service which then stores the photos in Azure Storage Blob storage. The storage account type is General-purpose V2. When photos are uploaded, they must be processed to produce and save a m...

The solution involves using Azure Blob Storage's change feed to trigger the photo processing workflow. Let’s evaluate if this solution meets the stated goal of processing the uploaded photo to create a mobile-friendly version in less than one minute. Azure Blob Storage Change Feed: - The change feed in Azure Blob Storage provides a way to track changes in blobs (like uploads or modifications). It delivers events for various operations on blobs, such as uploads, updates, and deletions. - Triggering the photo processing based on the change feed is a viable option. When a photo is uploaded to the storage account, the change feed would capture this event, which can then trigger a process to handle the photo transformation (such as generating the mobile-friendly version). - However, one critical consideration is that the change feed has some latency, which might be around a few seconds or up to a minute before the event is made available for processing. This means that while the event trigger is close to real-time, it may not always tri...

Author: Sophia · Last updated Jul 23, 2026

You are developing a web application that runs as an Azure Web App. The web application stores data in Azure SQL Database and stores files in an Azure Storage account. The web application makes HTTP requests to external services as part of normal operations. The web application is instrumented with Application Insights. The external services are OpenTelemetry co...

In this scenario, you are developing a web application that needs to ensure that the customer ID of the signed-in user is associated with all operations throughout the overall system. The goal is to correlate the customer ID with operations tracked by Application Insights and OpenTelemetry-compliant external services. Let’s review each option to understand which one best achieves this goal: Option A: Add the customer ID for the signed in user to the CorrelationContext in the web application - CorrelationContext is a way to associate contextual information, like user IDs, with telemetry data in distributed tracing systems (e.g., Application Insights and OpenTelemetry). - This option would allow the web application to inject the customer ID into the CorrelationContext. By doing so, the customer ID will be associated with all traces, requests, and other telemetry events generated by the application. This ensures that the customer ID is passed consistently across all operations and external service calls. - This approach is commonly used in distributed tracing scenarios, especially when you need to correlate user activity across various parts of the system. - Best option, as it maintains the customer ID context throughout the system and integrates well with both Azure Application Insights and OpenTelemetry tracing. Option B: On the current SpanContext, set the TraceId to the customer ID for the signed in user - The TraceId is a unique identifier for a trace. It typically refers to a specific operation or request and is shared across spans that make up that trace. - The TraceId is not designed to hold business-specific information like a customer ID. Using the TraceId for this purpose would break the conventions of distributed tracing and may interfere with the trace structure, making it hard to track trac...

Author: Isabella · Last updated Jul 23, 2026

SNAPSHOT - You are developing an Azure Function App. You develop code by using a language that is not supported by the Azure Function App host. The code language supports HTTP primitives. You must deploy the code to a production Azure Function App environment. You need to configure the app for deployment. Which configuration va...

Author: StarryEagle42 · Last updated Jul 23, 2026

DRAG DROP - You provision virtual machines (VMs) as development environments. One VM does not start. The VM is stuck in a Windows update process. You attach the OS disk for the affected VM to a recovery VM. You need to correct the issue. In which order should you perform the actions? To answer, m...

Author: Ava · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You develop an HTTP triggered Azure Function app to process Azure Storage blob data. The app is triggered using an output binding on the blob. The app continues to time ...

To address the issue of the HTTP-triggered Azure Function app timing out after four minutes, let's evaluate the proposed solution: Solution: Update the functionTimeout property of the host.json project file to 10 minutes. The `host.json` file contains configuration settings for Azure Functions, including the `functionTimeout` setting. This setting defines the maximum duration that a function is allowed to run before it times out. The default timeout for a function is 5 minutes for Consumption Plan and can be configured up to 60 minutes on a Premium Plan or Dedicated (App Service) Plan. Explanation of the Solution: 1. Timeout Setting: - By setting the `functionTimeout` to 10 minutes in the `host.json` file, this would extend the maximum execution time of the function. - This is applicable in scenarios where your function's processing time exceeds the default timeout of 5 minutes. 2. Scenarios Where This Works: - If you are running on a Premium Plan or Dedicated Plan (App Service Plan), this solution should work because you can configure the `functionTimeout` to up to 60 minutes. - This ...

Author: Vikram · Last updated Jul 23, 2026

SNAPSHOT - You are developing an Azure Durable Function based application that processes a list of input values. The application is monitored using a console application that retrieves JSON data from an Azure Function diagnostic endpoint. During processing a single instance of invalid input does not cause the function to fail. Invalid input must be available to the monitoring application. You need to implement the Azure Durable Function and the mo...

Author: Amelia · Last updated Jul 23, 2026

You are developing an Azure Durable Function to manage an online ordering process. The process must call an external API to gather product discount information. You need to implement the Azure Durable Function. Which Azure Durable Function types should...

Understanding Azure Durable Functions: Azure Durable Functions are part of the Azure Functions framework and allow you to write stateful workflows in a serverless environment. There are different types of Durable Functions for specific tasks: - Orchestrator Function: Coordinates and manages the execution of various tasks in a Durable Function workflow. It is responsible for the control flow of the entire process. - Activity Function: Performs individual tasks, such as calling external APIs or performing calculations. These are the building blocks that orchestrators invoke. - Client Function: Triggers the orchestration to start by sending the initial request and receiving the response. It acts as the client that starts the orchestration workflow. - Entity Function: Manages durable entities, which allow you to maintain stateful information across multiple function calls. These are typically used for scenarios like managing counters or other stateful operations. Given Scenario: - You are developing an Azure Durable Function to manage an online ordering process. - The process must call an external API to gather product discount information. To implement this, you need to identify the right types of functions to use based on the workflow and tasks. Explanation of Each Option: A) Orchestrator - The orchestrator function is ideal for this scenario because it coordinates the workflow. In this case, the orchestrator will manage the steps of the ordering process, including calling external APIs for discount information. - The orchestrator function will be responsible for determining the sequence of events (e.g., place order → fetch discount → apply discount → process payment). - It is not used for directly call...

Author: Aditya · Last updated Jul 23, 2026

DRAG DROP - You are authoring a set of nested Azure Resource Manager templates to deploy multiple Azure resources. The templates must be tested before deployment and must follow recommended practices. You need to validate and test the templates before deployment. Which tools should you use? To answer, drag the appropriate tools to the correct requirements. Each tool may be used once, more ...

Author: Elizabeth · Last updated Jul 23, 2026

You develop Azure Durable Functions to manage vehicle loans. The loan process includes multiple actions that must be run in a specified order. One of the actions includes a customer credit check process, which may require multiple days to process. You need...

Overview of Azure Durable Functions: Azure Durable Functions is designed to manage stateful workflows that require coordination across multiple tasks, especially when these tasks take varying lengths of time. The key types of functions are: - Orchestrator Function: Coordinates and manages the execution of multiple tasks. It controls the order of tasks, maintains state, and ensures that they are run in sequence. - Client Function: Starts the orchestrator function by triggering it. It is essentially the entry point that initiates the workflow. - Entity Function: Manages state over a long period of time, used for scenarios like counters, stateful data objects, or entity-based processes. - Activity Function: Executes individual tasks or actions, such as making API calls or performing computations. It is where the actual work happens. Scenario Breakdown: - The loan process includes multiple actions that must run in a specific order. - One of the actions involves a customer credit check, which may take multiple days to process. Which Azure Durable Function Type to Use? A) Orchestrator - The orchestrator function is the right choice to coordinate the entire vehicle loan process. The orchestrator ensures that all actions (like the credit check, approval, etc.) run in the specified order. - It can handle long-running workflows and waits for the completion of actions (like the credit check), even if it takes multiple days. - In this case, the orchestrator would: 1. Start the loan process. 2. Call the activity function for the credit check. 3. Wait for the credit check to complete (even if it takes multiple days). 4. Continue the process once the credit check is done. - The orchestrator can maintain the workflow’s state, making it ideal for this scenario. B) Client - The client function trigge...

Author: Sophia Clark · Last updated Jul 23, 2026

SNAPSHOT - You are developing an Azure Function app. All functions in the app meet the following requirements: * Run until either a successful run or until 10 run attempts occur. * Ensure that there are at least 20 seconds between attempts for up to 15 minutes. You need to configure the host.json file. How should y...

Author: Liam · Last updated Jul 23, 2026

You develop Azure Web Apps for a commercial diving company. Regulations require that all divers fill out a health questionnaire every 15 days after each diving job starts. You need to configure the Azure Web Apps so that the instance count scales up when divers are filling out the questionnaire and scales down after they are complete. You need to configure autoscaling. What a...

In this scenario, you're tasked with configuring autoscaling for Azure Web Apps in a commercial diving company, where divers fill out a health questionnaire every 15 days. The key goal is to scale up the instance count when divers are filling out the questionnaire and scale it down when they are finished. Let's evaluate each option: A) Recurrence Profile A Recurrence Profile allows you to configure autoscaling based on a set schedule, such as recurring events (e.g., every 15 days). Since the divers fill out the health questionnaire every 15 days, you could use a recurrence profile to scale up during the period when the questionnaires are being filled out and scale down once the period ends. - Why this works: You can set the autoscale to trigger based on the days and times when divers are expected to be filling out the questionnaires. - Best scenario: This configuration is ideal because you know the exact schedule (every 15 days), and it's easy to implement based on timing. B) CPU Usage-Based Autoscaling CPU usage-based autoscaling scales instances up or down based on the CPU utilization of the web app. If the CPU load increases significantly (e.g., when divers are filling out the questionnaire and submitting responses), this could trigger scaling events. - Why this is not ideal: While it’s useful for scaling based on load, there is no direct correlation between the CPU usage and the specific action of divers filling out the questionnaire. This may lead to scaling that’s not aligned with the actual activity, especially if the questionnaire filling process doesn’t consistently cause spikes in CPU usage. - Best scenario: This is typically used when you need to scale based on performance me...

Author: Aarav · Last updated Jul 23, 2026

SNAPSHOT - You are developing an online game that allows players to vote for their favorite photo that illustrates a word. The game is built by using Azure Functions and uses durable entities to track the vote count. The voting window is 30 seconds. You must minimize latency. You need to impleme...

Author: Emma · Last updated Jul 23, 2026

SNAPSHOT - You have an App Service plan named asp1 based on the Free pricing tier. You plan to use asp1 to implement an Azure Function app with a queue trigger. Your solution must minimize cost. You need to identify the configuration options that will meet the requirements. Which value shou...

Author: Maya · Last updated Jul 23, 2026

DRAG DROP - You are developing several microservices to run on Azure Container Apps. The microservices must allow HTTPS access by using a custom domain. You need to configure the custom domain in Azure Container Apps. In which order should you perform the ac...

Author: Sofia2021 · Last updated Jul 23, 2026

You are developing several microservices to run on Azure Container Apps. External HTTP ingress traffic has been enabled for the microservices. The microservices must be deployed to the same virtual network and write logs to...

When deploying several microservices to Azure Container Apps, several key requirements must be met: - The microservices should be deployed to the same virtual network. - They must be able to write logs to the same Log Analytics workspace. - External HTTP ingress traffic has been enabled. Now, let’s analyze each option based on the requirements: A) Enable Single Revision Mode Single revision mode means that only one version (revision) of the container will run at a time, preventing multiple revisions or versions of a service from running simultaneously. This limits the deployment flexibility. - Why it's not ideal: While this might simplify management by running only one revision, it doesn't directly address the need to deploy multiple microservices or allow them to write logs to the same workspace. It also restricts scaling, which might not be desirable in microservices scenarios. B) Use a Separate Environment for Each Container Creating separate environments for each container would mean deploying each microservice in a different isolated environment. This would require managing multiple environments, which could make networking and log aggregation more complex. - Why it's not ideal: Deploying microservices in separate environments would prevent them from being part of the same virtual network, which contradicts the requirement to deploy them to the same virtual network. It would also complicate the setup of a shared Log Analytics workspace. C) Use a Private Container Registry Image and Single Image for All Containers Using a private container registry allows you to securely store container images, but this is unrelated to the deployment method for the microservices themselves. The idea of using a single image for all containers doesn't fit the microservices architecture, where each microservice is usually built with its own image. - Why it's not ideal: While using a private registry is a good practice, it doesn’t address the deployment of microservices to the sa...

Author: Abigail · Last updated Jul 23, 2026

SNAPSHOT - You are developing several microservices to run on Azure Container Apps. External HTTP ingress traffic has been enabled for the microservices. A deployed microservice must be updated to allow users to test new features. You have the following requirements: * Enable and maintain a single URL for the updated microservice to provide to test users. * Update the microservice that corresponds to the current microservice version. Yo...

Author: Michael · Last updated Jul 23, 2026

SNAPSHOT - You plan to develop an Azure Functions app with an HTTP trigger. The app must support the following requirements: * Event-driven scaling * Ability to use custom Linux images for function execution You need to identify the app's hosting plan and the maximum amount of time that the app function can take to respond to incoming requests. Whic...

Author: Harper · Last updated Jul 23, 2026

SNAPSHOT - You develop a Python application for image rendering. The application uses GPU resources to optimize rendering processes. You have the following requirements: * The application must be deployed to a Linux container. * The container must be stopped whe...

Author: William · Last updated Jul 23, 2026

SNAPSHOT - You plan to develop an Azure Functions app with an Azure Blob Storage trigger. The app will be used infrequently, with a limited duration of individual executions. The app must meet the following requirements: * Event-driven scaling * Support for deployment slots * Minimize costs You need to identify the hosting plan and the maximum duration when executing the app...

Author: Zara · Last updated Jul 23, 2026

You are developing an ASP.NET Core app hosted in Azure App Service. The app requires custom claims to be returned from Microsoft Entra ID for user authorization. The claims must be removed when the app registration is re...

To include custom claims in the user access token in an ASP.NET Core app hosted in Azure App Service and ensure these claims are removed when the app registration is removed, let’s analyze the options one by one: A) Require the `https://graph.microsoft.com/.default` scope during authentication The `https://graph.microsoft.com/.default` scope is used to request Microsoft Graph API permissions. When you use this scope, it allows your app to access Microsoft Graph API resources (e.g., user data, calendar, mail), but it doesn’t control which claims are returned in the access token. - Why it's not ideal: While this scope is necessary for accessing Microsoft Graph API, it does not relate to configuring custom claims in the user access token for authorization. This option doesn’t address the problem of ensuring custom claims are returned in the user token. B) Configure the app to use the OAuth 2.0 authorization code flow The OAuth 2.0 authorization code flow is a standard flow for obtaining tokens and authorizing users. It is generally used for web apps or APIs to authenticate users and get access tokens and refresh tokens. - Why it's not ideal: Although the authorization code flow is a crucial part of authenticating users, it does not directly manage custom claims in the access token. The claims that are included in the token are determined by the Azure AD app configuration and the user’s assigned roles or groups, not the flow itself. Therefore, while this flow may be used for authentication, it doesn’t solve the issue of custom claims. C) Implement custom middleware to retrieve role information from Azure AD Custom middleware could be used to extract role information after the user has been authenticated, but it doesn’t directly affect the inclusion of custom claims in the user access token itself. - Why it's not ideal: This approach requires manual effort to handle claims in the middleware, and it doesn't provide a direct method t...

Author: Julian · Last updated Jul 23, 2026

You are developing a microservice to run on Azure Container Apps for a company. External HTTP ingress traffic has been enabled. The company requires that updates to the microservice must not cause ...

To ensure updates to the microservice don't cause downtime, we need a deployment strategy that supports seamless updates. Azure Container Apps provides different options for deploying and managing containers, and we need to select one that allows for no-downtime updates. Let’s analyze each option and reason out the best one. Option A: Enable single revision mode. - Explanation: In single revision mode, only one version (revision) of the container app can run at any given time. When an update is deployed, the old version is replaced by the new version. - Why rejected: This option would result in downtime because the new revision will replace the old one entirely. It doesn't support smooth traffic migration or blue/green deployments. Option B: Use multiple environments for each container. - Explanation: Using multiple environments means you create different environments (e.g., development, staging, production) for each container. These can be useful for isolating workloads but don’t directly solve the problem of zero-downtime updates. - Why rejected: While this allows you to have isolated deployments, it doesn’t automatically ensure zero downtime when updating a microservice. It introduces complexity with maintaining different environments, but the core issue of seamless updates still needs to be addressed separately. Option C: Use a private container registry and single image for all containers. - Explanation: A private container registry ensures that you can securely store and pull images for containers. While using a single image for all containers simplifies management, it doesn’t directly address zero-downtime updates. - Why rejected: This is more about container image management than deployment strategy. It doesn't provide a deployment me...

Author: Nathan · Last updated Jul 23, 2026

SNAPSHOT - A company uses Azure Container Apps. A container app named App1 resides in a resource group named RG1. The company requires testing of updates to App1. You enable multiple revision modes on App1. You need to ensure traffic is routed to each ...

Author: Isabella · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You deploy an Azure Container Apps app and disable ingress on the container app. Users report that they are unable to access the container app. You...

Scenario Explanation: In this case, the Azure Container Apps app has had ingress disabled, and users cannot access it. Furthermore, the app has scaled to 0 instances, which means no active containers are running to handle requests. We need to resolve this issue to ensure that the app is accessible again. Solution Evaluation: The proposed solution is to: - Enable ingress: This would allow external HTTP traffic to reach the container app. - Create an HTTP scale rule: This rule would ensure the app scales appropriately based on incoming HTTP traffic. - Apply the rule to the container app: This is necessary to ensure the scaling mechanism activates based on the traffic received. Why this solution is correct: 1. Enable ingress: If ingress is disabled, no external traffic can reach the container app. To resolve the access issue, ingress must be enabled. This will allow HTTP traffic to reach the app. 2. Create an HTTP scale rule: Since the container app has scaled down to 0 instances, it implies that the app hasn't been receiving traffic or isn’t configured to scale based on some criteria. Creating an HTTP scale rul...

Author: Liam · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You deploy an Azure Container Apps app and disable ingress on the container app. Users report that they are unable to access the container app. You ...

Scenario Explanation: In this case, the Azure Container App has ingress disabled, and users are unable to access the container app. Additionally, the app has scaled to 0 instances, meaning no containers are running. The goal is to resolve the issue and make the app accessible again. Solution Evaluation: The proposed solution involves: - Enable ingress: This would allow external HTTP traffic to reach the container app. - Create a custom scale rule: This involves defining a custom scaling condition to control when the app should scale based on specific metrics, such as CPU usage, memory, or custom application-specific metrics. - Apply the rule to the container app: This ensures that the custom scale rule is applied to the app and triggers the scaling behavior as intended. Why this solution might not meet the goal: 1. Enabling ingress: This part of the solution is correct, as enabling ingress will make the container app accessible from external traffic. Without ingress, users cannot access the app. 2. Custom scale rule: While creating a custom scale rule could be useful in some cases, it might not directly solve the problem of scaling from 0 instances. In this scenario, we are more concerned with ensuring the app scales based on incoming HTTP traffic, rather than relying on custom metrics or other conditions. A more standard approach (e.g., using an HTTP scale rule) would be simpler and more effective to scale the app automatically when HTTP traffic arrives. 3. Scaling from 0: The app is currently scaled to 0 instances, meani...

Author: Siddharth · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You deploy an Azure Container Apps app and disable ingress on the container app. Users report that they are unable to access the container app....

Scenario Explanation: The Azure Container App has ingress disabled, and users are unable to access it. Additionally, the app has scaled to 0 instances. The objective is to resolve the issue so users can access the app, ensuring that it scales correctly to avoid scaling to 0 instances and remains available. Solution Evaluation: The proposed solution involves: - Enable ingress: This step ensures that external HTTP traffic can reach the container app. Without ingress, no traffic can reach the app, making it inaccessible to users. - Configure the minimum replicas to 1: This ensures that there is at least one instance of the app running at all times. By setting the minimum replica count to 1, the app won't scale down to 0 instances, which addresses the issue of the app being unreachable when it has no running instances. Why this solution meets the goal: 1. Enabling ingress: This is necessary to allow external HTTP traffic to reach the container app. Without ingress, even if the app is running, it won't be accessible to users. 2. Configuring minimum replicas to 1: By configuring a minimum of 1 replica, we ensure that there is always at leas...

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 - M...

Author: Emily · Last updated Jul 23, 2026

DRAG DROP - You have an Azure Cosmos DB for NoSQL API account named account1 and a database named db1. An application named app1 will access db1 to perform read and write operations. You plan to modify the consistency levels for read and write operations performed by app1 on db1. You must enforce the consistency level on a per-operation basis whenever possible. You need to configure the consistency level for read and write operations. Which locations should you configure? To answer, move the appropriate l...

Author: Matthew · Last updated Jul 23, 2026

SNAPSHOT - You are creating an Azure Functions app project in your local development environment by using Azure Functions Core Tools. You must create the project in either Python or C# without using a template. You need to specify the command and its parameter required to create the Azure Functions app project. Which command ...

Author: Ahmed97 · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure App Service plan named APSPlan1 set to the Basic B1 pricing tier. APSPlan1 contains an App Servi...

Scenario Explanation: You have an Azure App Service plan named APSPlan1 set to the Basic B1 pricing tier, which contains an App Service web app named WebApp1. You plan to enable schedule-based autoscaling for APSPlan1, and the goal is to minimize the cost of running WebApp1 while enabling autoscaling. Solution Evaluation: The proposed solution is to scale down APSPlan1 to the Shared pricing tier. Why this solution does not meet the goal: 1. Scaling to the Shared pricing tier: The Shared (D1) pricing tier is a lower-cost option compared to the Basic B1 tier. However, the Shared tier has significant limitations that may not make it suitable for production workloads: - Limited scalability: The Shared pricing tier does not support autoscaling, which means you cannot enable schedule-based autoscaling with this tier. - Resource sharing: The Shared tier involves sharing resources with other customers, meaning performance can be inconsistent, and there is no guaranteed resource allocation. - Feature limitations: Autoscaling is not supported on the Shared tier. This is a key requirement in the scenario since you plan to enable...

Author: Chloe · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure App Service plan named APSPlan1 set to the Basic B1 pricing tier. APSPlan1 c...

Scenario Explanation: You have an Azure App Service plan named APSPlan1 set to the Basic B1 pricing tier. This plan contains an App Service web app named WebApp1. You plan to enable schedule-based autoscaling for APSPlan1, and the goal is to minimize the cost of running WebApp1. Solution Evaluation: The proposed solution is to scale out APSPlan1. Why this solution does not meet the goal: 1. Scaling out APSPlan1: Scaling out refers to increasing the number of instances of the App Service plan, which would increase the number of running instances to handle more traffic or load. This increases costs because more resources are being used. - Scaling out means you are adding additional instances to handle more load. While this may be necessary to support high traffic, it does not minimize costs. In fact, scaling out would likely increase costs since you would be paying for more instances. - Minimizing cost typically involves scaling in (reducing the number of instances) or choosing a more cost-effective pricing tier while still maintaining sufficient resources to support the application. 2. Goal of ...

Author: RadiantJaguar56 · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure App Service plan named APSPlan1 set to the Basic B1 pricing tier. APSPlan1 contains an App Servic...

The solution of scaling up APSPlan1 to the Premium V2 pricing tier will not meet the goal of minimizing the cost of running WebApp1. Key factors: 1. Pricing Tiers: The Basic B1 pricing tier is a lower-cost tier, while the Premium V2 pricing tier is designed for more advanced features and higher scalability, which comes at a significantly higher cost. 2. Scaling Considerations: The Premium V2 pricing tier offers features such as higher CPU, more memory, better scaling options, and additional capabilities like better performance and enhanced support for traffic spikes. However, these features come at a cost, and if the goal is to minimize the running cost, moving to a higher-priced tier (like Premium V2) contradicts that objec...

Author: Daniel · Last updated Jul 23, 2026

SNAPSHOT - You have an Azure Functions app using the Consumption hosting plan for a company. The app contains the following functions: You plan to enable dynamic concurrency on the app. The company requires that each function has its concurrency level managed separately. You need to configure the app for dynamic concurrency. Which ...

Author: Isabella · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You deploy an Azure Container Apps app and disable ingress on the container app. Users report that they are unable to access the container app. You...

The solution of enabling ingress, creating a TCP scale rule, and applying the rule to the container app does meet the goal. Key factors: 1. Ingress Disabled: When ingress is disabled on the Azure Container App, external traffic cannot reach the app, and since users are unable to access it, this is likely a cause of the problem. Enabling ingress is necessary to allow inbound traffic to the app. 2. Scaling to 0 Instances: If the container app scales down to 0 instances, it means that there is no active container running, so users cannot access the app. To resolve this, scaling rules need to be configured to ensure that the app maintains at least one instance running. 3. TCP Scale Rule: Creating a TCP scale rule would allow the app to sc...

Author: Noah · Last updated Jul 23, 2026

DRAG DROP - You have two Azure Container Registry (ACR) instances: ACR01 and ACR02. You plan to implement a containerized application named APP1 that will use a base image named BASE1. The image for APP1 will be stored in ACR01. The image BASE1 will be stored in ACR02. You need to automate the planned implementation by using a sequence of five Azure command-line interface (Azure CLI) commands. Your solution must ensure that the APP1 image stored in ACR01 will be automatically updated when the BASE1 image is updated. In which order should you perform the actions? To answer, move all co...

Author: Aria · Last updated Jul 23, 2026

SNAPSHOT - You plan to implement an Azure function named Function1 that will use the timer trigger. You plan to use a TimeSpan value to set the schedule of function execution. You need to select the hosting model and the schedule expression assignment method. Which hosting model and schedule expression assignm...

Author: Amira99 · Last updated Jul 23, 2026

SNAPSHOT - You are developing a microservices-based application that uses Azure Container Apps. The application consists of several containerized services that handle tasks, such as processing orders, managing inventory, and generating reports. You must secure the container apps. All apps must reside in the same virtual network, share the same Dapr configuration, and share the same logging location. Apps must support the configuration of the amount of memory and compute resources available to ...

Author: Noah · Last updated Jul 23, 2026

SNAPSHOT - You are developing a solution that uses the Azure Storage Client library for .NET. You have the following code: (Line numbers are included for reference only.) For each of the following statements, select Yes if the s...

Author: Zara1234 · Last updated Jul 23, 2026

You are building a website that uses Azure Blob storage for data storage. You configure Azure Blob storage lifecycle to move all blobs to the archive tier after 30 days. Customers have requested a service-level agreement (SLA) for viewing dat...

The correct SLA for data recovery from the archive tier in Azure Blob storage is A) at least two days. Key factors: 1. Archive Tier Characteristics: The archive tier is specifically designed for long-term storage of infrequently accessed data. When data is moved to the archive tier, it is not immediately accessible. Recovery from the archive tier involves rehydrating the data, which can take some time. 2. SLA for Archive Tier: Azure Blob Storage’s SLA for recovery from the archive tier is at least two days. This is the minimum time required to restore data from the archive tier to the hot or cool tiers for immediate access. 3. Other Options: - B) Between one and 15 hours: This SLA applies ...

Author: FrozenWolf2022 · Last updated Jul 23, 2026

SNAPSHOT - You are developing a ticket reservation system for an airline. The storage solution for the application must meet the following requirements: * Ensure at least 99.99% availability and provide low latency. * Accept reservations even when localized network outages or other unforeseen failures occur. * Process reservations in the exact sequence as reservations are submitted to minimize overbooking or selling the same seat to multiple travelers. * Allow simultaneous and out-of-order reservations with a maximum five-second tolerance window. You provision a resource group named airlineResourceGroup in the A...

Author: Jack · Last updated Jul 23, 2026

SNAPSHOT - You are preparing to deploy a Python website to an Azure Web App using a container. The solution will use multiple containers in the same container group. The Dockerfile that builds the container is as follows: You build a container by using the following command. The Azure Container Registry instance named images is a private registry. The user name and password for the registry is admin. The Web App must always run the same version of the website regardless of future builds. ...

Author: Carlos Garcia · Last updated Jul 23, 2026

SNAPSHOT - You are developing a back-end Azure App Service that scales based on the number of messages contained in a Service Bus queue. A rule already exists to scale up the App Service when the average queue length of unprocessed and valid queue messages is greater than 1000. You need to add a new rule that will continuously scale down the App Service as long as the scale up condition is no...

Author: Kai99 · Last updated Jul 23, 2026

DRAG DROP - You have an application that uses Azure Blob storage. You need to update the metadata of the blobs. Which three methods should you use to develop the solution? To answer, move the appropriate methods from t...

Author: BlazingPhoenix22 · Last updated Jul 23, 2026

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You are developing an Azure solution to collect point-of-sale (POS) device data from 2,000 stores located throughout the world. A single device can produce 2 megabytes (MB) of data every 24 hours. Each store location has one to five devices that send data. You must store the device data in Azure Blob storage. Dev...

The solution of provisioning an Azure Event Grid, configuring the machine identifier as the partition key, and enabling capture does not meet the goal. Key factors: 1. Azure Event Grid: Event Grid is primarily used for event-driven architectures and is designed for routing events between different services or systems in real-time. While it can be used to trigger actions based on events, it is not suitable for storing large volumes of data, such as the 2MB of data generated by each POS device every 24 hours. Event Grid does not provide a long-term data storage solution, which is needed in this case for storing device data in Azure Blob storage. 2. Partition Key & Capture: Configuring a partition key and enabling capture is generally more applicable to Azure Event Hubs for event streaming or to other services like Azure Data Lake Storage that focus on data storage. This is not directly applicable to Event Grid. While capture in Event Hubs allows for archiving and storing events, Event Grid does not have a built-in featu...

Author: Oscar · Last updated Jul 23, 2026

You develop Azure solutions. A .NET application needs to receive a message each time an Azure virtual machine finishes processing data. The messages must NOT persist after being processed by the receiving application. You...

To implement a .NET object that will receive messages in response to an Azure virtual machine finishing processing data, the correct object to use is A) QueueClient. Key factors: 1. QueueClient: This is a client object in Azure SDK for interacting with Azure Storage Queues. The scenario described specifies that the messages must not persist after being processed. Azure Storage Queues are designed for scenarios where messages are retrieved and processed by a consumer, and they can be deleted once processed, ensuring no persistence after consumption. This makes the QueueClient the right choice for receiving messages where persistence is not needed. 2. SubscriptionClient: This object is used to receive messages from an Azure Service Bus subscription. This is not suitable for the described use case because the scenario does not mention Service Bus topics or subscriptions. Additionally, while Service Bu...

Author: Elizabeth · Last updated Jul 23, 2026

DRAG DROP - You are maintaining an existing application that uses an Azure Blob GPv1 Premium storage account. Data older than three months is rarely used. Data newer than three months must be available immediately. Data older than a year must be saved but does not need to be available immediately. You need to configure the account to support a lifecycle management rule that moves blob data to archive storage for data not modified in the last year....

Author: William · 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 such as Azure Cosmos DB using the .NET API, the correct object to configure and execute requests is CosmosClient. Let’s go through the reasoning for selecting the correct option and rejecting the others: Explanation of Each Option: 1. A) `new Container(EndpointUri, PrimaryKey);` - The `Container` class is used to represent a specific container within a Cosmos DB database. A container in Cosmos DB is a collection of items, and you interact with it for operations like querying or writing data. However, `Container` requires an instance of `CosmosClient` to be created first, as it doesn't directly handle the connection or configuration to the Cosmos DB service itself. So, this option is not the right choice for initializing the connection to the database. 2. B) `new Database(EndpointUri, PrimaryKey);` - The `Database` class in Cosmos DB represents a logical container that holds multiple containers (collections). While `Database` is used after establishing a connection to the Cosmos DB instance, it doesn’t directly handle the connection initialization. Like the `Container`, it requires a `CosmosClient` object to interact with. Therefore, using just `Database(EndpointUri, PrimaryKey)` would be incorrect for creating the connection to Cosmos DB itself. 3. C) `new CosmosClient(EndpointUri, PrimaryKey);` - Correct Option: `CosmosClient` is the object that handles the connection to the Azure Cosmos DB instance. It is responsible for managing the connection, interacting with databases, and allowing operations like querying, inserting, and updati...

Author: MoonlitPantherX · Last updated Jul 23, 2026

You have an existing Azure storage account that stores large volumes of data across multiple containers. You need to copy all data from the existing storage account to a new storage account. The copy process must meet the following requirements: * Automate data movement. * Minimize u...

To automate the data movement, minimize user input, and ensure recoverability when copying large volumes of data across multiple containers in Azure storage, the best option is AzCopy. Let's break down why this is the best choice and why the other options are not suitable. Explanation of Each Option: 1. A) AzCopy - Correct Option: AzCopy is a command-line utility designed for high-performance data transfer to and from Azure storage accounts. It supports automating the data movement process, making it suitable for copying large volumes of data across multiple containers. AzCopy provides features like: - Automation: AzCopy can be scripted or scheduled, making it ideal for automating the transfer process. - Minimized user input: It is command-line driven, so no manual intervention is needed during the transfer process. - Recoverability: AzCopy has built-in resume and retry capabilities, ensuring that the data movement process is recoverable in case of network disruptions or failures. - Efficiency: It is optimized for high-performance data transfers, making it the best choice for copying large amounts of data. - Because of these features, AzCopy is perfect for moving large datasets with minimal user input and ensuring the process is automated and recoverable. 2. B) Azure Storage Explorer - Rejected Option: Azure Storage Explorer is a graphical interface tool for managing and interacting with Azure storage. While it allows users to copy data between storage accounts, it is not designed for automation: - It requires manual user intervention (you need to initiate the process manually). - It doesn’t provide the same level of automation or scripting capability as AzCopy. - While you can perform recoverable operations with Azure Storage Explorer, it is better suited for manual operations rather than large-scale, automated data transfers....

Author: Liam · Last updated Jul 23, 2026