How long will a Trusted Agent strive to replace a defective or inoperable token after receiving notification?

• A. 24 Hours
• B. 12 Hours
• C. 72 Hours
• D. 48 Hours

Answer: (A)

When a token is defective, the priority is to restore secure access as quickly as possible to minimize downtime and maintain security. A 24-hour timeframe is a practical one-day service level that many programs aim for, balancing the urgency of replacement with the realities of provisioning, verification, and delivery. Shorter windows like 12 hours, while ideal, may not be feasible in all scenarios due to logistical steps; longer windows such as 48 or 72 hours leave users offline longer and can increase risk or disruption. So the standard target is to strive for replacement within 24 hours.