Question 670
At Engineering Tower, iP phones boot in the data VLAN because the switch no longer advertises LLDP-MED voice policy. Which TWO responses together provide a direct implementation and a continuing safeguard for the stated risk? Select TWO answers.
Explanation
Correct Answers
This is the continuing risk-control element for Engineering Tower. Guard against arbitrary untrusted client VLAN tagging on shared ports prevents a future regression or unauthorized relaxation of the repair; it complements, rather than replaces, the implementation.
This is the implementation element for the Engineering Tower case: LLDP-MED can advertise voice-network attributes while the switch enforces separate VLAN policies. The specific action Advertise approved LLDP-MED voice VLAN and separate PC data access classification addresses the stated fault; the question also requires a persistent risk control.
Incorrect Answers
This may be an ongoing precaution for Tagged trunk allowlist: A VLAN trunk forwards only permitted tagged VLANs and its native VLAN according to configuration. It does not resolve the Voice VLAN LLDP-MED requirement in Engineering Tower and is not one of the two controls requested. The direct mechanism here is lLDP-MED can advertise voice-network attributes while the switch enforces separate VLAN policies
This may be a configuration step for Access VLAN classification: An access port carries untagged frames in one configured access VLAN. It does not resolve the Voice VLAN LLDP-MED requirement in Engineering Tower and is not one of the two controls requested. The direct mechanism here is lLDP-MED can advertise voice-network attributes while the switch enforces separate VLAN policies