Edge security is applied to inbound requests before policies from API Manager are applied.

Edge security is applied to inbound requests before policies from API Manager are applied.

• A. True
• B. False
• C. Only for outbound responses
• D. Not applied to inbound requests

Answer: (A)

Edge security at the API gateway runs on inbound requests first, before any API Manager policies are evaluated. It acts as the initial line of defense, handling protections like TLS termination, client certificate verification, IP allowlisting, and basic throttling or authentication checks. Only requests that pass these edge checks proceed to the API Manager policies for further governance, security, and transformation. So the statement is true because the edge layer processes inbound traffic before the API Manager policies are applied. The other options imply inbound requests aren’t secured or that edge protection only applies to outbound responses, which isn’t correct.

Edge security at the API gateway runs on inbound requests first, before any API Manager policies are evaluated. It acts as the initial line of defense, handling protections like TLS termination, client certificate verification, IP allowlisting, and basic throttling or authentication checks. Only requests that pass these edge checks proceed to the API Manager policies for further governance, security, and transformation. So the statement is true because the edge layer processes inbound traffic before the API Manager policies are applied. The other options imply inbound requests aren’t secured or that edge protection only applies to outbound responses, which isn’t correct.