Which statement is true about end-of-cryptoperiod changes?

Which statement is true about end-of-cryptoperiod changes?

• A. A daily rotation schedule
• B. The vendor's warranty terms
• C. The cryptoperiod for each key type and a process for key changes
• D. A password policy for users

Answer: (C)

The main idea here is how cryptographic keys are retired and replaced. Each key type has its own cryptoperiod—the time span from creation to decommission during which the key is considered valid and in use. End-of-cryptoperiod changes require a defined, formal process for rotating or retiring keys, applying new keys, and handling any necessary archival or destruction. This ensures keys don’t exceed their intended lifetime and that changes are auditable and controlled. Why this is the best fit: it directly ties end-of-cryptoperiod changes to two essential elements—the specific cryptoperiod for each key type and the procedure for performing key changes. That combination ensures proper lifecycle management rather than ad hoc or unrelated actions. Why the other ideas don’t fit: a daily rotation schedule is not universally correct because cryptoperiods vary by key type and policy. vendor warranty terms relate to support and hardware/software terms, not key lifecycle. a password policy for users concerns authentication credentials, not the cryptographic key lifecycle.

The main idea here is how cryptographic keys are retired and replaced. Each key type has its own cryptoperiod—the time span from creation to decommission during which the key is considered valid and in use. End-of-cryptoperiod changes require a defined, formal process for rotating or retiring keys, applying new keys, and handling any necessary archival or destruction. This ensures keys don’t exceed their intended lifetime and that changes are auditable and controlled.

Why this is the best fit: it directly ties end-of-cryptoperiod changes to two essential elements—the specific cryptoperiod for each key type and the procedure for performing key changes. That combination ensures proper lifecycle management rather than ad hoc or unrelated actions.

Why the other ideas don’t fit: a daily rotation schedule is not universally correct because cryptoperiods vary by key type and policy. vendor warranty terms relate to support and hardware/software terms, not key lifecycle. a password policy for users concerns authentication credentials, not the cryptographic key lifecycle.