Which event among the following is a trigger to change a lock combination?

Which event among the following is a trigger to change a lock combination?

• A. When the lock is initially placed in use
• B. When the keyboard is replaced
• C. After a power outage
• D. On the last day of the year

Answer: (A)

When a lock is first placed into service, that moment is used to set a new, known combination and distribute it only to authorized users. Establishing this initial credential creates a secure starting point so no one who might have known a previous or default code can access the lock. It’s about creating a controlled baseline for access from the very beginning. The other events aren’t standard triggers for changing the combination. Replacing the keyboard is a hardware maintenance action and may require reprogramming, but it’s not inherently the moment to change the code. A power outage doesn’t by itself mandate a change; once power is restored, the existing code remains valid unless a policy or incident calls for rekeying. End-of-year timing is arbitrary and not a security trigger unless a specific policy dictates calendar-based changes.

When a lock is first placed into service, that moment is used to set a new, known combination and distribute it only to authorized users. Establishing this initial credential creates a secure starting point so no one who might have known a previous or default code can access the lock. It’s about creating a controlled baseline for access from the very beginning.

The other events aren’t standard triggers for changing the combination. Replacing the keyboard is a hardware maintenance action and may require reprogramming, but it’s not inherently the moment to change the code. A power outage doesn’t by itself mandate a change; once power is restored, the existing code remains valid unless a policy or incident calls for rekeying. End-of-year timing is arbitrary and not a security trigger unless a specific policy dictates calendar-based changes.