What is wrong in the following description of the open source OpenStack Nova component?

Question

Options

• ANova relies on Keystone, Neutron, Glance, and Heat when creating virtual machines
• BIn some previous versions of OpenStack, Nova was responsible for implementing compute,
• CNova deploys Nova Compute on the control node to connect with hypervisors of different platforms
• DNova supports the management of bare metal, virtual machines, and containers

• A
  73% (27)
• B
  19% (7)
• D
  8% (3)

Explanation

Options A and C are the incorrect descriptions of Nova. Option A is wrong because while Nova does depend on Keystone (authentication), Neutron (networking), and Glance (image service) during VM creation, it does not rely on Heat. Heat is OpenStack's orchestration service that sits above Nova and can call Nova, but Nova itself has no dependency on Heat. Option C is wrong because Nova Compute is deployed on compute nodes, not the control node; the control node runs services like Nova API, Nova Conductor, and Nova Scheduler, while Nova Compute runs on the hosts that actually interact with hypervisors.

Option B is a valid historical fact - early OpenStack versions had Nova handling networking (Nova-Network) and volume management before those responsibilities were split into dedicated services like Neutron and Cinder. Option D is also accurate, as Nova supports virtual machines via hypervisors, bare metal via Ironic integration, and containers via relevant drivers.

Memory tip: For A, remember that Heat orchestrates Nova, not the other way around - the dependency arrow points downward from Heat to Nova, never up. For C, think "Compute runs on Compute nodes" - Nova Compute lives where the hypervisors live, not on the control plane.

No community discussion yet for this question.