MCD-LEVEL-1 practice question 14 of 30

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?

Full set: 235 questions
Answer options
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 Correct answer
Correct Answer:
D. Add required headers to the RAML specification and redeploy the new API proxy
Explanation

SLA-based policies (such as SLA-based Rate Limiting) require the client application to provide credentials, typically clientid and clientsecret. To properly enforce this policy and ensure that API consumers are aware of the requirement, the API's RAML specification must be updated to include these required headers (often implemented via a trait). Once the RAML is updated, the API proxy must be redeployed so that the new contract is active and the proxy can validate the incoming requests against the updated specification.

Why Incorrect

A: Property placeholders are used for internal application configuration, not for modifying the API contract to enforce client credentials. B: Environment variables configure the runtime environment but do not update the API specification to require SLA headers. C: Restarting the proxy clears caches but does not modify the API contract to enforce the required client ID and secret headers.

References

1. MuleSoft Official Documentation, "API Manager: SLA-based Rate Limiting Policy", Section: Prerequisites and Configuration.

2. MuleSoft Official Documentation, "Applying Policies and Client ID Enforcement", Section: Updating RAML for Policies.

Scroll to Top