AZ-204 Korean 無料問題集「Microsoft Developing Solutions for Microsoft Azure (AZ-204 Korean Version)」

Explanation:

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

Explanation:

解説: (JPNTest メンバーにのみ表示されます)

Explanation:

You can host native Linux applications in the cloud by using Azure Web Apps. To create a Web App for Containers, you must run Azure CLI commands that create a group, then a service plan, and finally the web app itself.
Step 1: az group create
In the Cloud Shell, create a resource group with the az group create command.
Step 2: az appservice plan create
In the Cloud Shell, create an App Service plan in the resource group with the az appservice plan create command.
Step 3: az webapp create
In the Cloud Shell, create a web app in the myAppServicePlan App Service plan with the az webapp create command. Don't forget to replace with a unique app name, and <docker-ID> with your Docker ID.
References:
https://docs.microsoft.com/mt-mt/azure/app-service/containers/quickstart-docker-go?view=sql-server-ver15

Explanation:

解説: (JPNTest メンバーにのみ表示されます)

解説: (JPNTest メンバーにのみ表示されます)

Explanation:

Box 1: user_impersonation
Box 2: delegated
Example:
1.Select the API permissions section
2.Click the Add a permission button and then:
Ensure that the My APIs tab is selected
3.In the list of APIs, select the API TodoListService-aspnetcore.
4.In the Delegated permissions section, ensure that the right permissions are checked: user_impersonation.
5.Select the Add permissions button.
Box 3: delegated
Example
1.Select the API permissions section
2.Click the Add a permission button and then,
Ensure that the Microsoft APIs tab is selected
3.In the Commonly used Microsoft APIs section, click on Microsoft Graph
4.In the Delegated permissions section, ensure that the right permissions are checked: User.Read. Use the search box if necessary.
5.Select the Add permissions button
References:
https://docs.microsoft.com/en-us/samples/azure-samples/active-directory-dotnet-webapp-webapi- openidconnect-aspnetcore/calling-a-web-api-in-an-aspnet-core-web-application-using-azure-ad/

Explanation:

Explanation:

Box 1: DynamicThresholdCriterion
Box 2: Http5xx
Server errors are in the 5xx range.
Client errors are in the 4xx range
Box 3: Low
Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-dynamic-thresholds

解説: (JPNTest メンバーにのみ表示されます)

Explanation:

Box 1: id
id is a unique identifier for the event.
Box 2: eventType
eventType is one of the registered event types for this event source.
Box 3: dataVersion
dataVersion is the schema version of the data object. The publisher defines the schema version.
Scenario: Authentication events are used to monitor users signing in and signing out. All authentication events must be processed by Policy service. Sign outs must be processed as quickly as possible.
The following example shows the properties that are used by all event publishers:
[
{
"topic": string,
"subject": string,
"id": string,
"eventType": string,
"eventTime": string,
"data":{
object-unique-to-each-publisher
},
"dataVersion": string,
"metadataVersion": string
}
]
Reference:
https://docs.microsoft.com/en-us/azure/event-grid/event-schema

Explanation:

Box 1: var key = await Resolver.ResolveKeyAsyn(keyBundle,KeyIdentifier.CancellationToken.None); Box 2: var x = new BlobEncryptionPolicy(key,resolver); Example:
// We begin with cloudKey1, and a resolver capable of resolving and caching Key Vault secrets.
BlobEncryptionPolicy encryptionPolicy = new BlobEncryptionPolicy(cloudKey1, cachingResolver); client.DefaultRequestOptions.EncryptionPolicy = encryptionPolicy; Box 3: cloudblobClient. DefaultRequestOptions.EncryptionPolicy = x; Reference:
https://github.com/Azure/azure-storage-net/blob/master/Samples/GettingStarted/EncryptionSamples
/KeyRotation/Program.cs