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-

Explanation

Box 1: Yes
The ItemDescription field in not searchable.
Box 2: No
The ItemDescription field in not searchable, but we would need to recreate the index.
Box 3: Yes
An indexer in Azure Search is a crawler that extracts searchable data and metadata from an external Azure data source and populates an index based on field-to-field mappings between the index and your data source.
This approach is sometimes referred to as a 'pull model' because the service pulls data in without you having to write any code that adds data to an index.
Box 4: No
References:
https://docs.microsoft.com/en-us/azure/search/search-what-is-an-index
https://docs.microsoft.com/en-us/azure/search/search-indexer-overview

Explanation

Metadata.Add example:
// Add metadata to the dictionary by calling the Add method
metadata.Add("docType", "textDocuments");
SetMetadataAsync example:
// Set the blob's metadata.
await blob.SetMetadataAsync(metadata);
// Set the blob's properties.
await blob.SetPropertiesAsync();
Reference:
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-properties-metadata

Explanation

Box 1: Premium
Service Bus can now emit events to Event Grid when there are messages in a queue or a subscription when no receivers are present. You can create Event Grid subscriptions to your Service Bus namespaces, listen to these events, and then react to the events by starting a receiver. With this feature, you can use Service Bus in reactive programming models.
To enable the feature, you need the following items:
A Service Bus Premium namespace with at least one Service Bus queue or a Service Bus topic with at least one subscription.
Contributor access to the Service Bus namespace.
Box 2: Contributor
Reference:
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-concept

Explanation

Plan: Standard
Standard support auto-scaling
Instance Count: 10
Max instances for standard is 10.
Scenario:
The REST API's that support the solution must meet the following requirements:
Allow deployment to a testing location within Azure while not incurring additional costs.
Automatically scale to double capacity during peak shipping times while not causing application downtime.
Minimize costs when selecting an Azure payment model.
References:
https://azure.microsoft.com/en-us/pricing/details/app-service/plans/