Question: In a 5G Edge Computing scenario, what is the primary purpose of collecting measurements related to EAS (Edge Application Server) discovery failure, considering factors like UE locations and application characteristics?
Option 1: To optimize EES (Edge Exposure Server) resource allocation for improved QoS (Quality of Service)
Option 2: To mitigate EAS discovery failure issues and trigger corrective actions (e.g., instantiating required EAS instances)
Option 3: To enhance security protocols for EEC (Edge Computing Engine) registration processes
Option 4: To monitor overall network latency in Edge Deployments
Explanation: Collecting measurements on EAS discovery failures, especially when analyzed through the lens of UE locations and application characteristics, allows for targeted interventions. By understanding where and why discoveries fail, operators can take corrective actions such as provisioning additional resources (e.g., instantiating more EAS instances in appropriate Edge Data Networks) to improve the success rate of EAS discoveries, thus enhancing overall edge computing performance.