Microsoft Developing Solutions for Microsoft Azure (AZ-204 Korean Version) - AZ-204 Korean Exam Practice Test

Explanation:

Explanation:

Box 1: Inbound.
A set-variable policy to store the detected user identity.
Example:
< policies >
< inbound >
< !-- How you determine user identity is application dependent -- >
< set-variable
name= " enduserid "
value= " @(context.Request.Headers.GetValueOrDefault( " Authorization " , " " ).Split( ' ' )[1].AsJwt()?.
Subject) " / >
Box 2: Inbound
A cache-lookup-value policy
Example:
< inbound >
< base / >
< cache-lookup vary-by-developer= " true | false " vary-by-developer-groups= " true | false " downstream- caching-type= " none | private | public " must-revalidate= " true | false " >
< vary-by-query-parameter > parameter name < /vary-by-query-parameter > < !-- optional, can repeated several times -- >
< /cache-lookup >
< /inbound >
Box 3: Outbound
A cache-store-value policy.
Example:
< outbound >
< base / >
< cache-store duration= " 3600 " / >
< /outbound >
Box 4: Outbound
A find-and-replace policy to update the response body with the user profile information.
Example:
< outbound >
< !-- Update response body with user profile-- >
< find-and-replace
from= ' " $userprofile$ " '
to= " @((string)context.Variables[ " userprofile " ]) " / >
< base / >
< /outbound >
Reference:
https://docs.microsoft.com/en-us/azure/api-management/api-management-caching-policies
https://docs.microsoft.com/en-us/azure/api-management/api-management-sample-cache-by-key

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

Explanation:

Box 1: allowedMemberTypes
allowedMemberTypes specifies whether this app role definition can be assigned to users and groups by setting to " User " , or to other applications (that are accessing this application in daemon service scenarios) by setting to " Application " , or to both.
Note: The following example shows the appRoles that you can assign to users.
" appId " : " 8763f1c4-f988-489c-a51e-158e9ef97d6a " ,
" appRoles " : [
{
" allowedMemberTypes " : [
" User "
],
" displayName " : " Writer " ,
" id " : " d1c2ade8-98f8-45fd-aa4a-6d06b947c66f " ,
" isEnabled " : true,
" description " : " Writers Have the ability to create tasks. " ,
" value " : " Writer "
}
],
" availableToOtherTenants " : false,
Box 2: User
Scenario: In order to review content a user must be part of a ContentReviewer role.
Box 3: value
value specifies the value which will be included in the roles claim in authentication and access tokens.
Reference:
https://docs.microsoft.com/en-us/graph/api/resources/approle

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

Explanation:

Scenario, Log policy: All Azure App Service Web Apps must write logs to Azure Blob storage.
Box 1: Status
Box 2: Succeeded
Box 3: operationName
Microsoft.Web/sites/write is resource provider operation. It creates a new Web App or updates an existing one.
Reference:
https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations

Explanation:

Box 1: orders o
Scenario: Order data is stored as nonrelational JSON and must be queried using SQL.
Box 2:li
Box 3: o.line_items
Box 4: o.city
The city field is in Order, not in the 2s.

Explanation:

Step 1: Create the Azure Functions app with a Consumption plan type.
Use the Consumption plan for serverless.
Step 2: Create a system-assigned managed identity for the application.
Create a system-assigned managed identity for your application.
Key Vault references currently only support system-assigned managed identities. User-assigned identities cannot be used.
Step 3: Create an access policy in Key Vault for the application identity.
Create an access policy in Key Vault for the application identity you created earlier. Enable the " Get " secret permission on this policy. Do not configure the " authorized application " or applicationId settings, as this is not compatible with a managed identity.
Reference:
https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references

Explanation:

Box 1: SecretClient
Box 2: DefaultAzureCredential
In below example, the name of your key vault is expanded to the key vault URI, in the format " https:// < your- key-vault-name > .vault.azure.net " . This example is using ' DefaultAzureCredential() ' class from Azure Identity Library, which allows to use the same code across different environments with different options to provide identity.
string keyVaultName = Environment.GetEnvironmentVariable( " KEY_VAULT_NAME " ); var kvUri = " https:// " + keyVaultName + " .vault.azure.net " ; var client = new SecretClient(new Uri(kvUri), new DefaultAzureCredential()); Reference:
https://docs.microsoft.com/en-us/azure/key-vault/secrets/quick-create-net

Explanation:

https://learn.microsoft.com/en-us/azure/api-management/include-fragment-policy