최신Microsoft Developing Microsoft Azure Solutions (070-532日本語版) - 070-532日本語무료샘플문제

Box 1:

Box 2:

Box 3:

Box 4:

Box 1: rate-limit-by-key
Box 2: counter-key
Box 3: @(context.Subscription.ID)
Limit call rate by key
The rate-limit-by-key policy prevents API usage spikes on a per key basis by limiting the call rate to a specified number per a specified time period. The key can have an arbitrary string value and is typically provided using a policy expression. Optional increment condition can be added to specify which requests should be counted towards the limit. When this policy is triggered the caller receives a 429 Too Many Requests response status code.
Syntax: <rate-limit-by-key calls="number"
renewal-period="seconds"
increment-condition="condition"
counter-key="key value" />
Example
In the following example, the rate limit is keyed by the caller IP address.
<policies>
<inbound>
<base />
<rate-limit-by-key calls="10"
renewal-period="60"
increment-condition="@(context.Response.StatusCode == 200)"
counter-key="@(context.Request.IpAddress)"/>
</inbound>
<outbound>
<base />
</outbound>
</policies>
Box 4: cors
The cors policy adds cross-origin resource sharing (CORS) support to an operation or an API to allow cross- domain calls from browser-based clients.
CORS allows a browser and a server to interact and determine whether or not to allow specific cross-origin requests (i.e. XMLHttpRequests calls made from JavaScript on a web page to other domains). This allows for more flexibility than only allowing same-origin requests, but is more secure than allowing all cross-origin requests.
Box 5: @(context.Subscription.ID)
Forward context information to the backend service
This example shows how to apply policy at the API level to supply context information to the backend service.
<!-- Copy this snippet into the inbound element to forward some context information, user id and the region the gateway is hosted in, to the backend service for logging or evaluation -->
<set-header name="x-request-context-data" exists-action="override">
<value>@(context.User.Id)</value>
<value>@(context.Deployment.Region)</value>
</set-header>