On the network shown in the figure, R1 serves as the gateway for PC2 and...

This scenario describes the classic router-on-a-stick inter-VLAN routing design. A single physical interface on R1 connects to switch S1, and multiple sub-interfaces are created on that physical interface to serve as gateways for multiple VLANs. Therefore, if R1 provides Layer 3 gateway functions for VLAN 2 and VLAN 3, sub-interfaces such as GE0/0/1.2 and GE0/0/1.3 must be configured, so option A is correct.

Because PC2 and PC3 are connected to switch S1, S1 learns their source MAC addresses dynamically and stores them in its MAC address table, making option B correct. R1 receives tagged frames from different VLANs on the trunk link and, through its sub-interfaces, can identify and terminate frames for VLAN 2 and VLAN 3, so option C is also correct. Option D is incorrect because hosts in different VLANs do not need to be connected to different physical switches; VLAN separation is logical, not necessarily physical. HCIA-Datacom uses this deployment to explain inter-VLAN communication, 802.1Q trunking, and flexible campus gateway design using limited router interfaces.