If an SLA based policy has been enabled in API Manager, what needs to be changed in the RAML specification?

When an SLA (Service Level Agreement) based policy is enabled in API Manager, it's essential to ensure that the API documentation reflects the updated requirements for the API consumers. Adding required headers to the RAML specification is critical because these headers often contain information that is necessary for implementing the SLA, such as quota limits, rate limits, or any other specific metadata related to the use of the API.

By updating the RAML specification to include these required headers, you ensure that potential clients are aware of the expectations and limitations set by the SLA policy. This not only aids in compliance but also helps developers who are using the API to understand how their requests will be handled and what parameters are needed for successful integration. After updating the RAML with the necessary headers, redeploying the API proxy allows these changes to take effect, ensuring that any requests made by clients are understood and processed in accordance with the new SLA terms.

In contrast, the remaining options do not directly address the need to inform API consumers about the SLA through the RAML specification and thus lack the necessary steps to ensure proper communication and integration of the SLA requirements.