Box 1: "oauth2Permissions": ["login"]
oauth2Permissions specifies the collection of OAuth 2.0 permission scopes that the web
API (resource) app exposes to client apps. These permission scopes may be granted to
client apps during consent.
Box 2: "oauth2AllowImplicitFlow":true

For applications (Angular, Ember.js, React.js, and so on), Microsoft identity platform
supports the OAuth 2.0 Implicit Grant flow.

A.

Consumption plan

D.

Step 1: Create an integration account in the Azure portal
You can define custom metadata for artifacts in integration accounts and get that metadata
during runtime for your logic app to use. For example, you can provide metadata for
artifacts, such as partners, agreements, schemas, and maps - all store metadata using
key-value pairs.
Step 2: Link the Logic App to the integration account
A logic app that's linked to the integration account and artifact metadata you want to use.
Step 3: Add partners, schemas, certificates, maps, and agreements
Step 4: Create a custom connector for the Logic App.
References:
https://docs.microsoft.com/bs-latn-ba/azure/logic-apps/logic-apps-enterprise-integrationmetadata

Scenario: Corporate website
While testing the site, the following error message displays:
CryptographicException: The system cannot find the file specified.
Step 1: Generate a certificate
Step 2: Upload the certificate to Azure Key Vault

Scenario: All SSL certificates and credentials must be stored in Azure Key Vault.
Step 3: Import the certificate to Azure App Service
Step 4: Update line SCO5 of Security.cs to include error handling and then redeploy the
code

A.

Azure Service Bus Queue

C.

Azure Service Bus Topic

Explanation:
The Azure Service Bus Queue and Topic has duplicate detection.
Enabling duplicate detection helps keep track of the application-controlled MessageId of all
messages sent into a queue or topic during a specified time window.
Reference:
https://docs.microsoft.com/en-us/azure/service-bus-messaging/duplicate-detection

Step 1: WORKDIR /apps/ContosoApp
Step 2: COPY ./-
The Docker document must be created in the same folder where ContosoApp.dll and
setupScript.ps1 are stored.
Step 3: EXPOSE ./ContosApp/ /app/ContosoApp
Step 4: CMD powershell ./setupScript.ps1
ENTRYPOINT ["dotnet", "ContosoApp.dll"]
You need to create a Dockerfile document that meets the following requirements:
Call setupScript.ps1 when the container is built.
Run ContosoApp.dll when the container starts.
References:
https://docs.microsoft.com/en-us/azure/app-service/containers/tutorial-custom-dockerimage

B.

No

To configure Manifest to include Group Claims in Auth Token

Go to Azure Active Directory to configure the Manifest. Click on Azure Active

Directory, and go to App registrations to find your application:

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

Manifest by clicking on it.

Locate the “groupMembershipClaims” setting. Set its value to either

“SecurityGroup” or “All”. To help you decide which:

“SecurityGroup” - groups claim will contain the identifiers of all security groups of

which the user is a member.

“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-aadgroups/