MCPA-LEVEL-1 practice question 15 of 15

What API policy would LEAST likely be applied to a Process API?

Full set: 95 questions
Answer options
A: Custom circuit breaker
B: Client ID enforcement
C: Rate limiting
D: JSON threat protection Correct answer
Correct Answer:
D. JSON threat protection
Explanation

In an API-led connectivity architecture, the Process API layer is responsible for orchestrating business processes by composing data from multiple System APIs. It is typically consumed by internal Experience APIs, not by external, untrusted clients. JSON Threat Protection is a security policy designed to guard against malicious payloads (e.g., oversized documents, deep nesting) that could cause denial-of-service attacks. This type of threat originates from external clients. Therefore, this policy is most appropriately applied at the edge of the application network—the Experience API layer—which is the primary entry point for external traffic. While security is important at all layers, this specific policy is least critical for a Process API that consumes data from other trusted, internal APIs.

Why Incorrect

A. Custom circuit breaker: Incorrect. Process APIs call downstream System APIs, making the circuit breaker pattern essential for resilience and preventing cascading failures when a System API is unresponsive.
B. Client ID enforcement: Incorrect. This is a fundamental governance policy used at all layers to identify, authorize, and track consuming applications, such as an Experience API calling a Process API.
C. Rate limiting: Incorrect. This policy is crucial for protecting the Process API and the underlying System APIs from being overloaded by a high volume of requests from Experience APIs.

References

1. MuleSoft Documentation, "API-Led Connectivity": This document outlines the three layers of API-led connectivity. It describes Experience APIs as the layer that provides a "means of accessing data, which is often reconfigured to be fit for purpose for a particular audience," implying this is the external-facing entry point. Process APIs are described as interacting with and shaping data from System APIs, indicating an internal role.

Source: MuleSoft Docs > Anypoint Platform > API-led Connectivity > "What is API-led Connectivity?".

2. MuleSoft Documentation, "JSON Threat Protection Policy": This document explains that the policy "protects your API from JSON-based content threats that can crash the parser and cause a denial of service." This is a typical security measure for public-facing or edge APIs that receive data from untrusted sources.

Source: MuleSoft Docs > Anypoint Platform > API Manager > Policies > "JSON Threat Protection Policy".

3. MuleSoft Documentation, "Circuit Breaker Policy": The documentation describes how a circuit breaker can "prevent client applications from continuing to call a backend API that is failing." This is directly applicable to a Process API that acts as a client to one or more backend System APIs.

Source: MuleSoft Docs > Anypoint Platform > API Manager > Policies > "Circuit Breaker".

4. MuleSoft Documentation, "Rate Limiting and Rate Limiting-SLA Policies" and "Client ID Enforcement Policy": These documents describe fundamental governance policies for controlling access and ensuring quality of service. They are applicable to any managed API, including Process APIs, to control how they are consumed by other layers like Experience APIs.

Source: MuleSoft Docs > Anypoint Platform > API Manager > Policies > "Rate Limiting and Rate Limiting-SLA Policies" and "Client ID Enforcement Policy".

Scroll to Top