Drag and Drop Question
You are developing a software solution for an autonomous transportation system. The solution uses large data sets and Azure Batch processing to simulate navigation sets for entire fleets of vehicles.
You need to create compute nodes for the solution on Azure Batch.
What should you do?

Correct Answer:

Explanation:
With the Azure Portal:
Step 1: In the Azure portal, create a Batch account.
First we create a batch account.
Step 2: In the Azure portal, create a pool of compute nodes Now that you have a Batch account, create a sample pool of Windows compute nodes for test purposes.
Step 3: In the Azure portal, add a Job.
Now that you have a pool, create a job to run on it. A Batch job is a logical group for one or more tasks. A job includes settings common to the tasks, such as priority and the pool to run tasks on.
Initially the job has no tasks.
Step 4: In the Azure portal, create tasks
Now create sample tasks to run in the job. Typically you create multiple tasks that Batch queues and distributes to run on the compute nodes.
References:
https://docs.microsoft.com/en-us/azure/batch/quick-create-portal

Comment: *

Name: *

Email: *

Verification: *

Hotspot Question
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 event 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 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.

Correct Answer:

Explanation:
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.
Reference:
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

Comment: *

Name: *

Email: *

Verification: *

You are building a website that is used to review restaurants. The website will use an Azure CDN to improve performance and add functionality to requests.
You build and deploy a mobile app for Apple iPhones. Whenever a user accesses the website from an iPhone, the user must be redirected to the app store.
You need to implement an Azure CDN rule that ensures that iPhone users are redirected to the app store.
How should you complete the Azure Resource Manager template? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Correct Answer:

Explanation

Box 1: iOS
Azure AD Conditional Access supports the following device platforms:
* Android
* iOS
* Windows Phone
* Windows
* macOS
Box 2: DeliveryRuleIsDeviceConditionParameters
The DeliveryRuleIsDeviceCondition defines the IsDevice condition for the delivery rule. parameters defines the parameters for the condition.
Box 3: HTTP_USER_AGENT
Box 4: DeliveryRuleRequestHeaderConditionParameters
DeliveryRuleRequestHeaderCondition defines the RequestHeader condition for the delivery rule. parameters defines the parameters for the condition.
Box 5: iOS
The Require approved client app requirement only supports the iOS and Android for device platform condition.
Reference:
https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-condition
https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-grant

Comment: *

Name: *

Email: *

Verification: *

You are developing a solution for a hospital to support the following use cases:
*The most recent patient status details must be retrieved even if multiple users in different locations have updated the patient record.
*Patient health monitoring data retrieved must be the current version or the prior version.
*After a patient is discharged and all charges have been assessed, the patient billing record contains the final charges.
You provision a Cosmos DB NoSQL database and set the default consistency level for the database account to Strong. You set the value for Indexing Mode to Consistent.
You need to minimize latency and any impact to the availability of the solution. You must override the default consistency level at the query level to meet the required consistency guarantees for the scenarios.
Which consistency levels should you implement? To answer, drag the appropriate consistency levels to the correct requirements. Each consistency level may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Correct Answer:

Explanation

Box 1: Strong
Strong: Strong consistency offers a linearizability guarantee. 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: Bounded staleness
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. 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
Box 3: Eventual
Eventual: There's no ordering guarantee for reads. In the absence of any further writes, the replicas eventually converge.

Comment: *

Name: *

Email: *

Verification: *

You are developing an Azure Function App that processes images that are uploaded to an Azure Blob container.
Images must be processed as quickly as possible after they are uploaded, and the solution must minimize latency. You create code to process images when the Function App is triggered.
You need to configure the Function App.
What should you do?

• A.Use an App Service plan. Configure the Function App to use an Azure Blob Storage input trigger.
• B.Use a Consumption plan. Configure the Function App to use an Azure Blob Storage trigger.
• C.Use a Consumption plan. Configure the Function App to use a Timer trigger.
• D.Use an App Service plan. Configure the Function App to use an Azure Blob Storage trigger.
• E.Use a Consumption plan. Configure the Function App to use an Azure Blob Storage input trigger.

Comment: *

Name: *

Email: *

Verification: *