You have been tasked with creating a dedicated virtual network between two local zones within a single system. In order to isolate the network traffic from other zones on that system. To accomplish…

Question

Options

• AAn ether stub
• BA virtual router
• CA virtual switch
• DA virtual bridge.
• EA virtual network interface
• FNothing because a virtual switch is automatically created then the virtual network interfaces are created.

• A
  82% (27)
• B
  3% (1)
• D
  9% (3)
• E
  3% (1)
• F
  3% (1)

Explanation

An etherstub (Oracle Solaris dladm create-etherstub) is a virtual datalink that acts as a self-contained, isolated network segment - VNICs from your target zones attach to it, and traffic stays entirely within that stub, invisible to all other zones on the system. This is the purpose-built Solaris mechanism for zone-to-zone network isolation.

Why the distractors are wrong:

• B (Virtual router): Routes traffic between networks; it doesn't create an isolated segment - it actually connects segments.
• C (Virtual switch): A conceptually adjacent idea, but not the Solaris-specific construct; the etherstub is the isolated virtual switching fabric.
• D (Virtual bridge): Bridges join existing network segments rather than creating a new isolated one.
• E (Virtual network interface/VNIC): VNICs are attached to the etherstub - they are the endpoints, not the isolated network itself.
• F (Nothing): Completely false; no isolation infrastructure is automatically provisioned when VNICs are created.

Memory tip: Think of an etherstub as a "private wire" - it only exists between the zones you explicitly plug into it. No plug, no access. The word stub hints that it goes nowhere else on the system - it dead-ends, creating the isolation.

No community discussion yet for this question.