Question 220
During a scheduled deployment at a municipal IT division in Portland, two sites use a policy requiring regular key replacement without visible downtime. The team is verifying its effect on citizen portals. Which acceptance outcome addresses the precise requirement?
Explanation
Correct Answer
At a municipal IT division in Portland, this verifies the specific ipsec tunnels requirement rather than merely recording an intended configuration: Traffic persists across a planned rekey and security association lifetimes update. The associated implementation is: configure supported IKE/IPSec rekey timers and compatible peer proposals.
Incorrect Answers
That observation measures quantum-resistant tunnel cryptography after this other intervention: Use a compatible explicitly negotiated algorithm selection or remain on a supported alternative pending upgrade. Its result is: Legacy peer compatibility is preserved or the unsupported combination is rejected before production cutover. The requested ipsec tunnels change is Configure supported IKE/IPSec rekey timers and compatible peer proposals, which must demonstrate: Traffic persists across a planned rekey and security association lifetimes update. The offered evidence does not validate the specified control.
The offered observation would confirm the separate intervention: Configure compatible IPSec tunnel parameters, routes, tunnel interface and Security policy. It measures: The negotiated IPSec tunnel carries encrypted traffic for the intended private prefixes only. The current ipsec tunnels configuration is Configure supported IKE/IPSec rekey timers and compatible peer proposals, and must demonstrate: Traffic persists across a planned rekey and security association lifetimes update. The two acceptance checks are not interchangeable even though they share a feature area.
The offered observation would confirm the separate intervention: Align the IKE gateway, authentication material and mutually supported cryptographic proposals. It measures: IKE and IPSec security associations are established for the expected peers. The current ipsec tunnels configuration is Configure supported IKE/IPSec rekey timers and compatible peer proposals, and must demonstrate: Traffic persists across a planned rekey and security association lifetimes update. The two acceptance checks are not interchangeable even though they share a feature area.