Microsoft AZ-204 Online Practice Questions and Exam Preparation

Microsoft AZ-204 Online Questions & Answers

• Question 91:

  HOTSPOT

  You are developing a ticket reservation system for an airline.

  The storage solution for the application must meet the following requirements:

  1. Ensure at least 99.99% availability and provide low latency.

  2. Accept reservations event when localized network outages or other unforeseen failures occur.

  3. Process reservations in the exact sequence as reservations are submitted to minimize overbooking or selling the same seat to multiple travelers.

  4. Allow simultaneous and out-of-order reservations with a maximum five-second tolerance window.

  You provision a resource group named airlineResourceGroup in the Azure South-Central US region.

  You need to provision a SQL SPI Cosmos DB account to support the app.

  How should you complete the Azure CLI commands? To answer, select the appropriate options in the answer area.

  NOTE: Each correct selection is worth one point.

  

  

  ---

  Box 1: BoundedStaleness

  Bounded staleness: The reads are guaranteed to honor the consistent-prefix guarantee. The reads might lag behind writes by at most "K" versions (that is, "updates") of an item or by "T" time interval. In other words, when you choose bounded staleness, the "staleness" can be configured in two ways:

  The number of versions (K) of the item

  The time interval (T) by which the reads might lag behind the writes

  Incorrect Answers:

  Strong

  Strong consistency offers a linearizability guarantee. Linearizability refers to serving requests concurrently. The reads are guaranteed to return the most recent committed version of an item. A client never sees an uncommitted or partial write.

  Users are always guaranteed to read the latest committed write.

  Box 2: --enable-automatic-failover true\

  For multi-region Cosmos accounts that are configured with a single-write region, enable automatic-failover by using Azure CLI or Azure portal. After you enable automatic failover, whenever there is a regional disaster, Cosmos DB will automatically failover your account.

  Question: Accept reservations event when localized network outages or other unforeseen failures occur.

  Box 3: --locations'southcentralus=0 eastus=1 westus=2 Need multi-region.

  https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

  https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/cosmos-db/manage-with-cli.md

• Question 92:

  Your company has an Azure subscription.

  You need to deploy a number of Azure virtual machines to the subscription by using Azure Resource Manager (ARM) templates. The virtual machines will be included in a single availability set.

  You need to ensure that the ARM template allows for as many virtual machines as possible to remain accessible in the event of fabric failure or maintenance.

  Which of the following is the value that you should configure for the platformUpdateDomainCount property?

  A. 10
  B. 20
  C. 30
  D. 40
  D. 40

  ---

  Explanation

  Each virtual machine in your availability set is assigned an update domain and a fault domain by the underlying Azure platform. For a given availability set, five non-user-configurable update domains are assigned by default (Resource Manager deployments can then be increased to provide up to 20 update domains) to indicate groups of virtual machines and underlying physical hardware that can be rebooted at the same time.

  https://docs.microsoft.com/en-us/azure/virtual-machines/windows/manage-availability

• Question 93:

  DRAG DROP

  You are developing an Azure solution to collect inventory data from thousands of stores located around the world. Each store location will send the inventory data hourly to an Azure Blob storage account for processing.

  The solution must meet the following requirements:

  1. Begin processing when data is saved to Azure Blob storage.

  2. Filter data based on store location information.

  3. Trigger an Azure Logic App to process the data for output to Azure Cosmos DB.

  4. Enable high availability and geographic distribution.

  5. Allow 24-hours for retries.

  6. Implement an exponential back off data processing.

  You need to configure the solution.

  What should you implement? To answer, select the appropriate options in the answer area.

  NOTE: Each correct selection is worth one point.

  Select and Place:

  

  

  ---

  Box 1: Azure Event Grid

  Blob storage events are pushed using Azure Event Grid to subscribers such as Azure Functions, Azure Logic Apps, or even to your own http listener. Event Grid provides reliable event delivery to your applications through rich retry policies and dead-lettering.

  Box 2: Azure Logic App

  Event Grid uses event subscriptions to route event messages to subscribers. This image illustrates the relationship between event publishers, event subscriptions, and event handlers.

  

  Box 3: Azure Service Bus

  The Event Grid service doesn't store events. Instead, events are stored in the Event Handlers, including ServiceBus, EventHubs, Storage Queue, WebHook endpoint, or many other supported Azure Services.

  https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-event-overview

  https://docs.microsoft.com/en-us/java/api/overview/azure/messaging-eventgrid-readme

• Question 94:

  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. Device data must be correlated based on a device identifier. Additional stores are expected to open in the future.

  You need to implement a solution to receive the device data.

  Solution: Provision an Azure Service Bus. Configure a topic to receive the device data by using a correlation filter.

  Does the solution meet the goal?

  A. Yes
  B. No
  A. Yes

  ---

  Explanation

  A message is raw data produced by a service to be consumed or stored elsewhere. The Service Bus is for high-value enterprise messaging, and is used for order processing and financial transactions.

  https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services

• Question 95:

  HOTSPOT

  You are developing a content management application for technical manuals. The application is deployed as an Azure Static Web app.

  Authenticated users can view pages under/manuals but only contributors can access the page /manuals/new.html.

  You need to configure the routing for the web app.

  How should you complete the configuration? To answer, select the appropriate options in the answer area.

  NOTE: Each correct selection is worth one point.

  

  

  ---

  Box 1: /manuals/new.html

  Note:

  Rules are evaluated in the order as they appear in the routes array.

  Rule evaluation stops at the first match. A match occurs when the route property and a value in the methods array (if specified) match the request. Each request can match at most one rule.

  Box 2: contributors

  Only contributors have access to /manuals/new.html

  Box 3: /manuals*

  Box 4: authenticated

  All authenticated users have access to the manuals.

  https://learn.microsoft.com/en-us/azure/static-web-apps/configuration

• Question 96:

  You develop and deploy an Azure App Service web app to a production environment. You enable the Always On setting and the Application Insights site extensions.

  You deploy a code update and receive multiple failed requests and exceptions in the web app.

  You need to validate the performance and failure counts of the web app in near real time.

  Which Application Insights tool should you use?

  A. Snapshot Debugger
  B. Profiler
  C. Smart Detection
  D. Live Metrics Stream
  E. Application Map
  D. Live Metrics Stream

  ---

  Explanation

  Live Metrics Stream

  Deploying the latest build can be an anxious experience. If there are any problems, you want to know about them right away, so that you can back out if necessary. Live Metrics Stream gives you key metrics with a latency of about one second.

  With Live Metrics Stream, you can: * Validate a fix while it's released, by watching performance and failure counts.

  * Etc.

  

  Incorrect:

  * Profiler

  Azure Application Insights Profiler provides performance traces for applications running in production in Azure. Profiler:

  Captures the data automatically at scale without negatively affecting your users.

  Helps you identify the "hot" code path spending the most time handling a particular web request.

  * Snapshot debugger

  When an exception occurs, you can automatically collect a debug snapshot from your live web application. The snapshot shows the state of source code and variables at the moment the exception was thrown. The Snapshot Debugger in Azure Application Insights monitors exception telemetry from your web app. It collects snapshots on your top-throwing exceptions so that you have the information you need to diagnose issues in production.

  https://docs.microsoft.com/en-us/azure/azure-monitor/app/live-stream

• Question 97:

  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.

  Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

  Select and Place:

  

  

  ---

  Step 1: Upgrade the storage account to GPv2

  Object storage data tiering between hot, cool, and archive is supported in Blob Storage and General Purpose v2 (GPv2) accounts. General Purpose v1 (GPv1) accounts don't support tiering.

  You can easily convert your existing GPv1 or Blob Storage accounts to GPv2 accounts through the Azure portal.

  Step 2: Copy the data to be archived to a Standard GPv2 storage account and then delete the data from the original storage account

  Step 3: Change the storage account access tier from hot to cool

  Note: Hot - Optimized for storing data that is accessed frequently.

  Cool - Optimized for storing data that is infrequently accessed and stored for at least 30 days.

  Archive - Optimized for storing data that is rarely accessed and stored for at least 180 days with flexible latency requirements, on the order of hours.

  Only the hot and cool access tiers can be set at the account level. The archive access tier can only be set at the blob level.

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

• Question 98:

  You are developing several Azure API Management (APIM) hosted APIs.

  You must make several minor and non-breaking changes to one of the APIs. The API changes include the following requirements:

  Must not disrupt callers of the API.

  Enable roll back if you find issues.

  Documented to enable developers to understand what is new.

  Tested before publishing.

  You need to update the API.

  What should you do?

  A. Configure and apply header-based versioning.
  B. Create and publish a product.
  C. Configure and apply a custom policy.
  D. Add a new revision to the API.
  E. Configure and apply query string-based versioning.
  E. Configure and apply query string-based versioning.

  ---

  Explanation

  Versioning schemes

  Different API developers have different requirements for versioning. Azure API Management doesn't prescribe a single approach to versioning, but instead provides several options.

  Path-based versioning

  Header-based versioning

  When the header versioning scheme is used, the version identifier needs to be included in an HTTP request header for any API requests. You can specify the name of the HTTP request header.

  Query string-based versioning

  When the query string versioning scheme is used, the version identifier needs to be included in a query string parameter for any API requests. You can specify the name of the query string parameter.

  Note: Versions in Azure API Management

  Versions allow you to present groups of related APIs to your developers. You can use versions to handle breaking changes in your API safely. Clients can choose to use your new API version when they're ready, while existing clients continue to use an older version. Versions are differentiated through a version identifier (which is any string value you choose), and a versioning scheme allows clients to identify which version of an API they want to use.

  For most purposes, each API version can be considered its own independent API. Two different API versions might have different sets of operations and different policies.

  With versions you can:

  Publish multiple versions of your API at the same time.

  Use a path, query string, or header to differentiate between versions.

  Use any string value you wish to identify your version, which could be a number, a date, or a name.

  Show your API versions grouped together on the developer portal.

  Take an existing (non-versioned) API, and create a new version of it without breaking existing clients.

  https://learn.microsoft.com/en-us/azure/api-management/api-management-versions

• Question 99:

  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 over time.

  You need to select a partition key.

  Which two partition keys can you use? Each correct answer presents a complete solution.

  NOTE: Each correct selection is worth one point.

  A. a single property value that does not appear frequently in the documents
  B. a value containing the collection name
  C. a single property value that appears frequently in the documents
  D. a concatenation of multiple property values with a random suffix appended
  E. a hash suffix appended to a property value
  D. a concatenation of multiple property values with a random suffix appended
  E. a hash suffix appended to a property value

  ---

  Explanation

  You can form a partition key by concatenating multiple property values into a single artificial partitionKey property. These keys are referred to as synthetic keys.

  Another possible strategy to distribute the workload more evenly is to append a random number at the end of the partition key value. When you distribute items in this way, you can perform parallel write operations across partitions.

  Note: It's the best practice to have a partition key with many distinct values, such as hundreds or thousands. The goal is to distribute your data and workload evenly across the items associated with these partition key values. If such a property doesn't exist in your data, you can construct a synthetic partition key.

  https://docs.microsoft.com/en-us/azure/cosmos-db/synthetic-partition-keys

• Question 100:

  HOTSPOT

  You are developing an Azure Function App by using Visual Studio. The app will process orders input by an Azure Web App. The web app places the order information into Azure Queue Storage.

  You need to review the Azure Function App code shown below.

  

  NOTE: Each correct selection is worth one point.

  

  

  ---

  Box 1: No

  ExpirationTime - The time that the message expires.

  InsertionTime - The time that the message was added to the queue.

  Box 2: Yes

  maxDequeueCount - The number of times to try processing a message before moving it to the poison queue. Default value is 5.

  Box 3: Yes

  When there are multiple queue messages waiting, the queue trigger retrieves a batch of messages and invokes function instances concurrently to process them. By default, the batch size is 16. When the number being processed gets down to 8, the runtime gets another batch and starts processing those messages. So the maximum number of concurrent messages being processed per function on one virtual machine (VM) is 24.

  Box 4: Yes

  References:

  https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-queue