The correct solution is to establish a trunk connection between Switch A and Switch B. Computer A and Computer B are both connected to access VLAN 1 on their local switches. However, the inter-switch link appears to be configured as an access port in VLAN 8. Because the link between the switches is not carrying VLAN 1 traffic, devices in VLAN 1 on separate switches cannot communicate across that connection.

The CompTIA Network+ N10-009 objectives include VLANs, switching, trunking, access ports, and troubleshooting Layer 2 connectivity. Access ports carry traffic for a single VLAN. Trunk ports carry traffic for multiple VLANs between switches, usually using tagging such as IEEE 802.1Q. To allow VLAN 1 devices on both switches to communicate, the inter-switch connection must carry VLAN 1 traffic. A trunk would allow VLAN 1 and other required VLANs to pass between the switches.

Link aggregation is not the issue, and Gi0/10 is administratively down. Spanning Tree Protocol prevents loops but does not fix missing VLAN transport. Changing both hosts to a /24 would not solve the VLAN separation problem and could make IP reachability worse. Therefore, trunking is required.