Free Cisco 400-007 Actual Exam Questions - Question 5 Discussion
(Choose three.)
I’m going with B, C, and D as well. Cisco Open Virtual Switch (B) is needed for the virtual networking layer, Nexus switches (C) handle the physical network infrastructure, and UCS (D) provides the compute platform. A and E seem more related to service management and containers, which aren’t core NFVi components here. F is a virtual network function itself, not the infrastructure. So, B, C, and D fit best as the main products used with Red Hat for NFVi.
B/C/D? The Open Virtual Switch is essential for the virtual networking layer, Nexus switches cover the physical network infrastructure, and UCS handles compute resources. These three align well with what’s needed for NFVi alongside Red Hat. A and E seem more related to service management or container platforms, which don’t fit directly into the NFVi stack. F sounds like a function rather than infrastructure, so it’s less likely here.
B/C/D? The Open Virtual Switch (B) and Nexus switches (C) handle networking layers, while UCS (D) provides the compute infrastructure—sounds like the classic NFVi mix with Red Hat.
Maybe B, C, and D. The Open Virtual Switch (B) is key for virtual networking, Nexus (C) handles physical switching, and UCS (D) covers the compute side, which fits the NFVi setup with Red Hat.
Maybe A, C, and D. I’m thinking Prime Service Catalog (A) could help manage the NFVi services alongside the hardware parts—Nexus (C) and UCS (D) cover switching and compute, so these three make sense.
I don’t think Prime Service Catalog (A) fits here since it’s more about service management rather than NFVi infrastructure. The core NFVi components should be Cisco UCS for compute (D), Nexus switches for networking hardware (C), and the Open Virtual Switch for virtual networking (B). So I’d go with B, C, and D based on what Cisco typically uses for Red Hat NFVi setups.
You're right about UCS and Nexus being core. I’d swap Open Container Platform (E) out since it’s more for containers, so B, C, and D seems solid for NFVi basics. B
B, D, and C make the most sense because UCS handles compute, Nexus covers switching, and Open Virtual Switch is key for virtual networking with Red Hat. E feels more container-focused than core NFVi.
A, D, and E since Prime helps with service catalog, UCS is compute, and Open Container supports NFVi.
D imo, since UCS is the main hardware for compute, and C because Nexus provides the needed network fabric. B fits as it’s Cisco’s virtual switch, essential for virtualized environments alongside Red Hat.
C imo, since Nexus is critical for network infrastructure alongside UCS (D).
Maybe B, D, and F since Open Virtual Switch and UCS provide the virtual and physical infrastructure, and Virtual Network Function fits with NFVi’s service aspect. Nexus switches (C) might be more about traditional networking, less NFVi-specific here.
It’s B, C, and D since UCS is the hardware and Nexus handles switching layers.
B/D/E? I’m ruling out A because Prime Service Catalog is more for service management, not NFVi itself. E might fit since Open Container Platform supports container orchestration alongside Red Hat.
B/C/D? I’m picking those because Cisco UCS (D) handles the compute hardware, Nexus (C) covers the network switching, and Open Virtual Switch (B) manages the virtual networking layer. The other options don’t seem to fit NFVi roles as directly—like Prime Service Catalog is more about service management and Open Container Platform focuses on containers, not NFVi infrastructure. So, B, C, and D make the most sense for an NFVi setup with Red Hat.
B (Open Virtual Switch), C (Nexus), and D (UCS) fit best with NFVi setups.
The question is about NFVi, so networking gear like Cisco Nexus (C) definitely plays a role alongside UCS (D) and Open Virtual Switch (B). So I’d pick B, C, and D.
B/D/E? The Open Virtual Switch and UCS are obvious, and the Open Container Platform fits with Red Hat’s container angle. Not sure about the others.