APIC enforces a maximum number of concurrent login sessions per user. A common scripting mistake is calling the login endpoint inside a loop (once per object created/queried) instead of authenticating once and reusing the resulting session cookie/token for all subsequent requests - this rapidly exhausts the session limit and results in login/authorization failures. Simply adding sleep delays (Option A) does not address the underlying issue of session exhaustion. This tests understanding of APIC session management at scale, an important operational/scripting consideration.