A municipal 311 API needs new custom authentication that inspects several request headers and a query parameter. The team is wiring an OCI Functions authorizer to API Gateway. Which authorizer shape should they choose for a new implementation?
Select an answer to reveal the explanation.
Short Explanation
Picture a night watchman who can check badge, clipboard, and guest list at once instead of only one badge. Oracle’s recommended custom path is a multi-argument authorizer that can read several request elements. Single-argument authorizers still work but are the older form headed for deprecation—new custom auth should be multi-argument.
Full Explanation
OCI API Gateway Functions authorizers support multi-argument authorizers that accept several request elements (headers, query, host). Single-argument authorizers remain supported but are the older form and are planned for deprecation. A multi-argument function can also accept a single header token when that is all you need. New custom authentication should be implemented as a multi-argument authorizer; do not design new work around the single-argument shape.