What is the next step to configure the API proxy to enforce the new SLA policy?

An SLA based policy has been enabled in API Manager.

What is the next step to configure the API proxy to enforce the new SLA policy?
A . Add new property placeholders and redeploy the API proxy
B . Add new environment variables and restart the API proxy
C . Restart the API proxy to clear the API policy cache
D . Add required headers to the RAML specification and redeploy the new API proxy

View Answer

Answer: D

Explanation:

Correct answer is Add required headers to RAML specification and redeploy new API proxy

MuleSoft Doc Ref: https://docs.mulesoft.com/api-manager/2.x/tutorial-manage-an-api

Steps are as below:

Add the Required RAML Snippet

SLA-based rate limiting requires adding a RAML or OAS snippet to your API. This procedure demonstrates adding a RAML snippet.

Specify the client ID and secret as query parameters.

Add a section called traits: at the RAML root level to define query parameters:

traits:

– client-id-required: queryParameters: client_id:

type: string client_secret: type: string

Add the client-id-required trait to every method that requires these query parameters: /users:

get:

is: [client-id-required]

description: Gets a list of JSONPlaceholder users.

Step 2: Add the SLA Tier in API Manager

Step 3: Apply the policy and redeploy

Reference: https://docs.mulesoft.com/api-manager/2.x/tutorial-manage-an-api