Which two possible drawbacks should you consider when introducing Network Functions Virtualization in a network design? (Choose two)

NFV does not inherently increase bandwidth utilization; it changes where and how traffic is processed but does not add traffic to the network by design.

While suboptimal traffic flows are possible in some NFV deployments, this is a configuration outcome rather than a fundamental or universally applicable drawback of introducing NFV into a design.

Virtualizing network functions requires server or routing platforms with substantial CPU, memory, and fast I/O capabilities - equivalent to high-end hardware - to match the throughput and latency that purpose-built ASICs deliver in traditional network appliances.

NFV does not require OpenFlow; OpenFlow is a southbound SDN protocol independent of NFV, which can be deployed with or without SDN control plane protocols.

NFV depends on an orchestration and management framework - defined by the ETSI NFV MANO architecture including the NFV Orchestrator, VNF Manager, and Virtual Infrastructure Manager - which adds significant architectural complexity and a new operational dependency to the network design.