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

Correct Answer:

Explanation

Scenario:
Order data is stored as nonrelational JSON and must be queried using Structured Query Language (SQL). The Order data is stored in a Cosmos database.

Correct Answer:

Explanation

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

Correct Answer: A  🗳️

Explanation: Only visible for ValidVCE members. You can sign-up / login (it's free).

Correct Answer:

Explanation