An administrator creates a Private VLAN with a Primary VLAN ID of 2. The administrator than creates three Private VLANs as follows: Marketing PVLAN ID. 4 PVLAN Type. Isolated Accounting PVLAN ID. 5…

Question

Options

• AChange the PVLAN type for the Accounting network to Promiscuous.
• BChange the PVLAN ID for the Accounting network to 2.
• CChange the PVLAN type for Marketing network to Promiscuous.
• DChange the PVLAN ID for Accounting network to 4.

• A
  63% (33)
• C
  23% (12)
• D
  13% (7)

Explanation

In Private VLANs, Isolated ports can ONLY communicate with Promiscuous ports - they cannot communicate with other Isolated ports, even across different secondary VLANs. Since both Accounting (PVLAN 5) and Marketing (PVLAN 4) are Isolated, they are blocked from communicating with each other. To resolve this: (A) Changing Accounting's type to Promiscuous allows it to communicate with all PVLAN types, including isolated Marketing ports, because isolated ports can send to promiscuous ports and vice versa. (B) Changing Accounting's PVLAN ID to 2 (the Primary VLAN ID) effectively places Accounting ports into the promiscuous domain, achieving the same result as option A - ports in the primary VLAN are promiscuous by definition. Option C might seem plausible but is not selected because changing the Marketing servers to promiscuous was not identified as the intended resolution in this exam scenario; the correct fix is to change the Accounting (the side reporting problems) network. Option D is wrong because placing Accounting into PVLAN ID 4 still results in two Isolated ports in the same secondary VLAN, and isolated ports cannot communicate with each other regardless.

No community discussion yet for this question.