Question 750
A security requirement calls for traffic between finance and engineering to traverse an inspected firewall, yet the fabric team tries to merge the routing zones directly. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
This control reduces recurrence of the same class of failure: Tenant routing-zone isolation is an intentional boundary; intertenant reachability may require an approved external routing/security service rather than indiscriminate VRF route sharing. Apply the recurring practice: Require application-owner and security approval for any new route or policy linking routing zones. The previous example was: A security requirement calls for traffic between finance and engineering to traverse an inspected firewall, yet the fabric team tries to merge the routing zones directly.
Incorrect Answers
Verify server-facing tagging requirements whenever a host changes operating system or virtualization configuration. That concerns tenant VLAN tagging through connectivity template, while the issue here is intertenant communication via external policy device. Design the supported external system path with explicit routing policies and firewall controls for only the approved source, destination and service.
Routing-zone connectivity and security policy authorization are distinct requirements when business traffic crosses controlled service boundaries. For this issue, design the supported external system path with explicit routing policies and firewall controls for only the approved source, destination and service.
Include connectivity-template assignment checks in endpoint onboarding and movement workflows. Here, tenant routing-zone isolation is an intentional boundary; intertenant reachability may require an approved external routing/security service rather than indiscriminate VRF route sharing.