Question: How does a source GTP-C entity enforce overload control for traffic destined to a peer GTP-C entity in direct contact?
Option 1: Based on the available bandwidth of the source GTP-C entity.
Option 2: Based on the overload reduction metric received from the peer GTP-C entity.
Option 3: Based on the priority of the messages being sent.
Option 4: Based on the number of active sessions with the peer GTP-C entity.
Explanation: The source GTP-C entity enforces overload control based on the information received from the peer GTP-C entity, specifically the overload reduction metric. This allows the source entity to adjust its traffic accordingly and prevent overloading the peer entity.