Which capability is provided by API Portal that supports consumer developers but is not primarily a design-time feature?

• A. API testing in a try-it-out environment
• B. RAML design editing
• C. Policy management
• D. Access control for consuming applications

Answer: (D)

Access control for consuming applications is the capability that directly supports consumer developers by handling how their apps access APIs. It lets developers register their applications, obtain credentials (like API keys or OAuth tokens), and define which APIs, with what scopes and quotas, their apps are allowed to call. This is a runtime, governance function—enforced at the gateway to manage and secure access for each consumer app—rather than something you do while designing the API.

Try-it-out testing environments help developers experiment with endpoints, but they don’t provision or manage access for consuming apps. RAML design editing is a design-time task focused on defining the API contract, not managing runtime access. Policy management configures gateway policies, which is also more about how APIs behave rather than how individual consumer applications are granted access.