Key History functionality includes:

Key History functionality includes:

• A. Storing certificate information to allow use of older keys
• B. Generating new keys on demand
• C. Reverting to older system policies
• D. Tracking login attempts

Answer: (A)

Key History functionality focuses on maintaining a record of previously used keys and certificates so the system can still work with data protected by older keys. This is crucial during key rotation or certificate updates, because you may need to verify signatures or decrypt data that was created with past keys. By storing certificate information and the associated keys in history, the system can provide continuity, enable audits, and ensure access to legacy communications or documents without forcing immediate, permanent changes. That’s why storing certificate information to allow use of older keys is the best fit. It directly supports cryptographic agility and operational continuity across key lifecycles. Generating new keys on demand is about producing fresh keys rather than keeping track of past ones. Reverting to older system policies relates to policy versions, not cryptographic history. Tracking login attempts deals with authentication activity, not key history.

Key History functionality focuses on maintaining a record of previously used keys and certificates so the system can still work with data protected by older keys. This is crucial during key rotation or certificate updates, because you may need to verify signatures or decrypt data that was created with past keys. By storing certificate information and the associated keys in history, the system can provide continuity, enable audits, and ensure access to legacy communications or documents without forcing immediate, permanent changes.

That’s why storing certificate information to allow use of older keys is the best fit. It directly supports cryptographic agility and operational continuity across key lifecycles. Generating new keys on demand is about producing fresh keys rather than keeping track of past ones. Reverting to older system policies relates to policy versions, not cryptographic history. Tracking login attempts deals with authentication activity, not key history.