Question 620
Before approving a proposed shortcut for the following case—An internal Layer 3 firewall separates private-cloud segments but a static route remains after the old next hop is retired—which risk should be considered first?
Explanation
Correct Answer
The issue is not a general product inconvenience: A healthy firewall interface does not prove the route to the destination is still valid. That matters for an internal Layer 3 firewall separates private-cloud segments but a static route remains after the old next hop is retired. The design should document the corresponding investigation and practical acceptance evidence.
Incorrect Answers
This would be appropriate for “A security architect budgets a private-cloud TLS proxy using the firewall's peak cleartext packet rate”. The design should document the corresponding investigation and practical acceptance evidence. Here the decisive requirement is “A healthy firewall interface does not prove the route to the destination is still valid”.
The alternative deals with “A datacenter runs both BGP and OSPF routing around firewalls, and an ECMP change creates asymmetric stateful flows”. The expected safe result is that two-way test flows remain symmetric and survive documented route changes. The current question instead selects “A healthy firewall interface does not prove the route to the destination is still valid”.
The option applies in “A private cloud hosts internal applications but the organization relies solely on an external perimeter firewall to protect core services”. The expected safe result is that unauthorized access to protected core apps is denied and approved internal services remain available. That evidence does not directly establish “A healthy firewall interface does not prove the route to the destination is still valid” for the scenario at hand.