Question: In a 3GPP Northbound API framework, what is the primary purpose of making the API invoker's associated authentication information available at the Application Enablement Function (AEF) after initial authentication with the Common API Framework (CAPIF) core function?
Option 1: To enhance security by requiring dual-factor authentication for every API call.
Option 2: To reduce latency during subsequent API invocations by pre-authenticating the API invoker.
Option 3: To enable the AEF to cache API responses for frequent queries, improving overall system efficiency.
Option 4: To facilitate anonymous API calls by masking the API invoker's identity from the AEF.
Explanation: The correct answer, Option 2, highlights the key benefit of pre-authenticating and storing the API invoker's authentication information at the AEF. This approach streamlines subsequent interactions by minimizing the overhead associated with repeated authentication processes, thus reducing latency during API invocations. This is particularly important in real-time or low-latency applications within telecom networks, where swift data exchange is crucial for service quality.