Question: What is a potential cause of GTP-C overload when a large number of users are transitioning between idle and connected mode?
Option 1: Insufficient internal resource capacity of a GTP-C entity
Option 2: Deficiency of a GTP-C entity component leading to reduced overall performance
Option 3: Traffic flood resulting from frequent TAU/RAU procedures by a large number of users
Option 4: Exceptional event locally generating a traffic spike due to a catastrophic event
Explanation: A traffic flood resulting from frequent Tracking Area Update (TAU) or Routing Area Update (RAU) procedures by a large number of users can cause GTP-C overload. This is because each TAU/RAU procedure generates signalling traffic, and when a large number of users perform these procedures simultaneously, it can lead to a sudden increase in signalling traffic, causing an overload on the GTP-C entity.