Consider the following commands and output on the local server: Also, consider the following route table entry on a remote system: 192.168.2.0 192.168.1.200 UG 1 1 You must configure a virtual…

Question

Exhibits

Options

• Aipadm set-ifprop -p forwarding=on net0
• Bipadn set-prop -p forwarding=on vnic2
• Cipacim set-prop -p forwarding=on ipv4
• Dipadm set-prop -p routing=on net0
• Erouteadm -ue ipv4-forwarding
• Frouteadm -ue ipv4-routing

• A
  76% (22)
• B
  7% (2)
• D
  14% (4)
• E
  3% (1)

Explanation

Enabling IP forwarding in Oracle Solaris requires action at two levels: the interface level and the system/protocol level. Option A (ipadm set-ifprop -p forwarding=on net0) correctly uses set-ifprop (interface property) to enable forwarding on the specific physical interface net0, while option F (routeadm -ue ipv4-forwarding) enables and persists IPv4 packet forwarding system-wide - both are required for the virtual switch to route packets to the remote 192.168.2.0 network via 192.168.1.200.

Why the distractors fail:

• B uses the misspelled command ipadn and the wrong subcommand set-prop (which targets protocol-level properties, not interface properties) - it would also need set-ifprop
• C invents a non-existent command ipacim
• D uses ipadm set-prop (protocol-level) with the wrong property name routing instead of forwarding; even if corrected, it targets the wrong scope for an interface
• E uses routeadm -ue ipv4-routing, which enables the dynamic routing daemon (in.routed) - not packet forwarding; routing ≠ forwarding in Solaris

Memory tip: In Solaris, think "two-layer sandwich" - ipadm set-ifprop handles the interface slice (net0), and routeadm -ue ipv4-forwarding handles the system slice. Also remember: forwarding = passing packets, routing = running a routing protocol - the exam loves to swap these terms.

No community discussion yet for this question.