How will setting the Purpose field within the network definition of a server profile impact the network traffic?

Question

Options

• Anetwork purpose can give higher priority for a specific type of traffic
• Bnetwork purpose will impact the traffic only if Virtual Connect modules are used
• Cnetwork purpose will define QoS within Logical Interconnect
• Dnetwork purpose does not affect the behavior of the network

• A
  2% (1)
• B
  2% (1)
• D
  96% (43)

Explanation

Option D is correct because the Purpose field in an HPE OneView network definition is purely metadata - it acts as an administrative label to help identify the intended use of a network (e.g., Management, iSCSI, FCoE), but it does not alter how traffic is processed, prioritized, or routed in any way.

Why the distractors are wrong:

• A is incorrect because traffic prioritization is handled by QoS policies, not the Purpose field - setting Purpose to "iSCSI" does not actually give iSCSI traffic higher priority.
• B is incorrect because the Purpose field's behavior (or lack of it) is not conditional on the presence of Virtual Connect modules; it's irrelevant to traffic regardless of the interconnect technology.
• C is incorrect because QoS within a Logical Interconnect is defined through QoS configuration in Logical Interconnect Groups, not through the network Purpose field.

Memory tip: Think of the Purpose field like a sticky note on a cable - it tells you what it's for, but it doesn't change how electricity flows through it. If you need to actually affect traffic behavior, look to QoS policies and Logical Interconnect Group settings instead.

No community discussion yet for this question.