Question: In 3GPP Northbound APIs, what is the primary purpose of dynamically configuring the address of the Application Function Entity (AEF) providing the Service API to the AEF entry point in API topology hiding management?
Option 1: To enable secure communication between PLMN trust domain and 3rd party trust domain by concealing internal network topology.
Option 2: To simplify the process of onboarding new services by automatically assigning IP addresses within the PLMN.
Option 3: To enhance QoS (Quality of Service) for specific applications by prioritizing their traffic through dedicated AEFs.
Option 4: To facilitate load balancing across multiple AEF instances providing the same Service API.
Explanation: The correct answer is Option 1 because dynamically configuring the address of the AEF in the context of API topology hiding management primarily aims to conceal the internal network structure from external entities, thereby enhancing security. This is particularly relevant when interactions occur between different trust domains (e.g., PLMN and 3rd party), as it prevents exposure of sensitive network details.