Correct Answer:

Box 1: internal caching-type Choose between the following values of the attribute:

1.

internal to use the built-in API Management cache,

2.

external to use the external cache as Azure Cache for Redis

3.

prefer-external to use external cache if configured or internal cache otherwise.

4.

Box 2: private

downstream-caching-type

This attribute must be set to one of the following values.

1.

none - downstream caching is not allowed.

2.

private - downstream private caching is allowed.

3.

public - private and shared downstream caching is allowed.

Box 3: Authorization Authorization

Note: Start caching responses per value of specified header, such as Accept, Accept-Charset, Accept-Encoding, Accept-Language, Authorization, Expect, From, Host, If-Match

Reference: https://docs.microsoft.com/en-us/azure/api-management/api-management-caching-policies

Correct Answer:

Box 1: ApplicationInsightsLoggerOptions

If you want to include the EventId and EventName properties, then add the following to the ConfigureServices method:

services

AddOptions()

Configure(o => o.IncludeEventId = true);

Box 2: IncludeEventID

Microsoft AZ-204

Box 3: ApplicationServices

In Asp.Net core apps it turns out that trace logs do not show up in Application Insights out of the box. We need to add the following code snippet to our Configure method in Startup.cs:

loggerFactory.AddApplicationInsights(app.ApplicationServices, logLevel);

References:

https://blog.computedcloud.com/enabling-application-insights-trace-logging-in-asp-net- core/

Correct Answer:

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.

Incorrect Answers:

Consistent prefix: Updates that are returned contain some prefix of all the updates, with no gaps. Consistent prefix guarantees that reads never see out-of-order writes.

Reference:

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

Correct Answer:

Correct Answer: A

To configure Manifest to include Group Claims in Auth Token

1.

Go to Azure Active Directory to configure the Manifest. Click on Azure Active Directory, and go to App registrations to find your application:

2.

Click on your application (or search for it if you have a lot of apps) and edit the Manifest by clicking on it.

3.

Locate the “groupMembershipClaims” setting. Set its value to either “SecurityGroup” or “All”. To help you decide which:

1.

“SecurityGroup” - groups claim will contain the identifiers of all security groups of which the user is a member.

2.

“All” - groups claim will contain the identifiers of all security groups and all distribution lists of which the user is a member

Now your application will include group claims in your manifest and you can use this fact in your code.

Reference:

https://blogs.msdn.microsoft.com/waws/2017/03/13/azure-app-service-authentication-aad-groups/

Correct Answer: B

Create an Azure Function App that uses an Azure Service Bus Queue trigger.

Reference: https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-storage-queue-triggered-function

Correct Answer: CD

Azure Functions is the simplest option if you are just getting started using the change feed. Due to its simplicity, it is also the recommended option for most change feed use cases. When you create an Azure Functions trigger for Azure Cosmos DB, you select the container to connect, and the Azure Function gets triggered whenever there is a change in the container. Because Azure Functions uses the change feed processor behind the scenes, it automatically parallelizes change processing across your container's partitions.

Note: You can work with change feed using the following options:

1.

Using change feed with Azure Functions

2.

Using change feed with change feed processor

Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/read-change-feed https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed-pull-model https://docs.microsoft.com/en-us/azure/cosmos-db/read-change-feed#azure-functions https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed-pull-model#using-feedrange-for-parallelization

Correct Answer: A

A service SAS is secured with the storage account key. A service SAS delegates access to a resource in only one of the Azure Storage services: Blob storage, Queue storage, Table storage, or Azure Files.

Stored access policies give you the option to revoke permissions for a service SAS without having to regenerate the storage account keys.

Incorrect Answers:

Account SAS: Account SAS is specified at the account level. It is secured with the storage account key.

User Delegation SAS: A user delegation SAS applies to Blob storage only.

Reference:

https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview

Correct Answer: CDF

Correct Answer: D

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.

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

Correct Answer: C

Data Connect grants a more granular control and consent model: you can manage data, see who is accessing it, and request specific properties of an entity. This enhances the Microsoft Graph model, which grants or denies applications

access to entire entities.

Microsoft Graph Data Connect augments Microsoft Graph's transactional model with an intelligent way to access rich data at scale. The data covers how workers communicate, collaborate, and manage their time across all the applications

and services in Microsoft 365.

Incorrect:

Not B: The Microsoft Graph API is a RESTful web API that enables you to access Microsoft Cloud service resources. After you register your app and get authentication tokens for a user or service, you can make requests to the Microsoft

Graph API.

A simplistic definition of a Graph API is an API that models the data in terms of nodes and edges (objects and relationships) and allows the client to interact with multiple nodes in a single request.

Not C: Microsoft Graph connectors, your organization can index third-party data so that it appears in Microsoft Search results.

With Microsoft Graph connectors, your organization can index third-party data so that it appears in Microsoft Search results.

Reference: https://docs.microsoft.com/en-us/graph/data-connect-concept-overview

Correct Answer: AB

The Durable Functions extension exposes a set of built-in HTTP APIs that can be used to perform management tasks on orchestrations, entities, and task hubs. These HTTP APIs are extensibility webhooks that are authorized by the Azure Functions host but handled directly by the Durable Functions extension.

Reference: https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-http-api

Correct Answer: B

Correct Answer: D

Explanation:

A service bus instance has already been created (Step 2 below). Next is step 3, Create a Service Bus queue.

Note:

Steps:

Step 1: # Create a resource group

resourceGroupName="myResourceGroup"

az group create --name $resourceGroupName --location eastus

Step 2: # Create a Service Bus messaging namespace with a unique name

namespaceName=myNameSpace$RANDOM

az servicebus namespace create --resource-group $resourceGroupName --name $namespaceName --location eastus

Step 3: # Create a Service Bus queue

az servicebus queue create --resource-group $resourceGroupName --namespace-name $namespaceName --name BasicQueue

Step 4: # Get the connection string for the namespace

connectionString=$(az servicebus namespace authorization-rule keys list --resource-group $resourceGroupName --namespace-name $namespaceName --name RootManageSharedAccessKey --query primaryConnectionString --output tsv)

Reference:

https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-cli

Correct Answer: ABD

Scenario: You must perform a point-in-time restoration of the retail store location data due to an unexpected and accidental deletion of data.

Before you enable and configure point-in-time restore, enable its prerequisites for the storage account: soft delete, change feed, and blob versioning.

Reference:

https://docs.microsoft.com/en-us/azure/storage/blobs/point-in-time-restore-manage