Which of the following lists contain items you should verify when you are troubleshooting a failed switch change VLAN action? Select one:

Troubleshooting a failed "Change VLAN" action requires verifying four key areas. First, compatibility must be confirmed at the specific Switch Model level, as support for actions can vary even within the same vendor. Second, the managing appliance (not the Enterprise Manager) must have write permissions (e.g., SNMP read-write community string or CLI credentials with sufficient privilege) to alter the switch's configuration. Third, the network path must allow the necessary protocols for configuration changes, which are SSH (for CLI) or SNMP Set, to travel from the managing appliance to the switch. Finally, the action itself must be enabled within the policy; a disabled action will not execute.

A. This is incorrect because actions are performed by the managing appliance, not the Enterprise Manager. It also incorrectly lists SNMP Get/Trap, which are for reading data and receiving alerts, not for writing configuration changes.

B. This is incorrect because "read" access is insufficient to change a VLAN configuration; write access is required. It also incorrectly specifies SNMP Get, which is a read-only protocol.

D. This is incorrect because it specifies "read" access, which is insufficient for a configuration change. Also, stating a vendor is "compatible for all actions" is an inaccurate overgeneralization.

1. Forescout Switch Plugin Configuration Guide v8.3.1, Page 11, Section: "Configure the Switch for Forescout Platform Management". This section states, "To let the Forescout platform apply actions that change the switch configuration, you must configure read/write access credentials for the switch." This confirms the need for write access. The same section also details the required protocols: "The Forescout platform can manage switches using the following protocols: SNMP, CLI (Telnet or SSH)," which implies SNMP Set for write operations.

2. Forescout Switch Plugin Configuration Guide v8.3.1, Page 12, Section: "Configure SNMP on the Switch". This section explicitly differentiates between read-only and read-write community strings, stating, "To apply actions that change the switch configuration, define a Read-Write Community String." This directly supports the requirement for write access and the use of SNMP Set.

3. Forescout Administration Guide v8.3, Page 491, Section: "Working with Policies". This section details policy creation and management, explaining that actions within a rule must be enabled to be applied to matching endpoints. This confirms the need to verify that the action is enabled.

4. Forescout Switch Plugin Configuration Guide v8.3.1, Appendix A: "Supported Vendors and Products". This appendix provides a detailed matrix of supported actions broken down by vendor and specific switch model, confirming that compatibility checks must be done at the model level, not just the vendor level.