What CANNOT be effectively enforced using an API policy in Anypoint Platform?
What CANNOT be effectively enforced using an API policy in Anypoint Platform?
Backend system overloading cannot be effectively enforced using an API policy in Anypoint Platform. API policies in Anypoint Platform are designed to enforce security, traffic management, and other operational guidelines for APIs. Nonetheless, preventing backend system overloading requires handling unexpected spikes in traffic, resource limitations, and other factors that go beyond what API policies can manage. Effective strategies to avoid backend overloading include load balancing, scaling, and capacity planning, which must be implemented at the system architecture level.
Guarding against Denial of Service attacks
DoS attack prevention is part of Anypoint security for Edge, and not API Policies. https://docs.mulesoft.com/anypoint-security/index-policies
Found this online: Which three events can be effectively enforced using an API policy in Anypoint Platform? (Choose three.) A Log HTTP requests and responses B Authenticate credentials between APIs C Prevent overloading the back-end system D Identify denial-of-service attacks E Application auto-restart F Stack overload prevention index A, B and C are correct. So that means in this question on Examtopics the correct answer is A
Backend system overloading cannot be effectively enforced using an API policy in Anypoint Platform. API policies in Anypoint Platform can help enforce security, traffic management, and other requirements for APIs. However, they cannot effectively prevent backend system overloading. This is because overloading can occur due to various factors such as unexpected spikes in traffic or resource limitations, which cannot be controlled by API policies alone. To prevent overloading, additional measures such as load balancing, scaling, and capacity planning need to be implemented at the backend system level.
A is correct
Answer: A