Question 40
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A service provider deploys virtual firewalls across multiple compute nodes but ignores the shared virtual-switch and storage dependencies. Which continuing control best reduces recurrence of this problem?
Explanation
Correct Answer
For this scenario, the observed situation is: A service provider deploys virtual firewalls across multiple compute nodes but ignores the shared virtual-switch and storage dependencies. The most directly supported response is: Design NFV infrastructure capacity and redundancy for compute, switching, and storage beneath the VNFs. Technical basis: NFVI provides the virtualized resources on which individual VNF workloads depend. Evidence of success: A controlled compute-host failure leaves the engineered virtual network function available under stated limits. Ongoing protection: Test infrastructure failure domains and reserve CPU and packet I/O headroom.
Incorrect Answers
The alternative guards against: AAA separates authentication, authorization, and accounting while TACACS+ supports centralized device administration. The root condition for this case is: NFVI provides the virtualized resources on which individual VNF workloads depend. The focused prevention check is: Test infrastructure failure domains and reserve CPU and packet I/O headroom.
The alternative guards against: BGP prefix filtering and suppression constrain what peers can inject into routing policy. The root condition for this case is: NFVI provides the virtualized resources on which individual VNF workloads depend. The focused prevention check is: Test infrastructure failure domains and reserve CPU and packet I/O headroom.
That recurring practice manages a separate exposure: DWDM multiplexes optical channels, while Ethernet VLAN tags distinguish packet-level service membership. The present case instead depends on: NFVI provides the virtualized resources on which individual VNF workloads depend. The suitable ongoing safeguard is: Test infrastructure failure domains and reserve CPU and packet I/O headroom.