READ Free Dumps For Cisco- 300-135
| Question ID 15421 | A customer network engineer has made configuration changes that have resulted in some
PC2 in VLAN 200 is unable to ping the gateway address 172.16.200.1; identify the issue. |
| Option A | VTP domain name mismatch on SW4 |
| Option B | VLAN 200 not configured on SW1 |
| Option C | VLAN 200 not configured on SW2 |
| Option D | VLAN 200 not configured on SW4 |
| Option F | Answer : C Explanation: By looking at the configuration for SW2, we see that it is missing VLAN 200, and the switchport access vlan 200 command is missing under interface eth 0/0:
|
| Correct Answer | F |
| Question ID 15422 | A customer network engineer has made configuration changes that have resulted in some
Refer to the topology. |
| Option A | Management VLAN not allowed in the trunk links between SW1 and SW4 |
| Option B | Management VLAN not allowed in the trunk links between SW1 and SW2 |
| Option C | Management VLAN not allowed in the trunk link between SW2 and SW4 |
| Option D | Management VLAN ip address on SW4 is configured in wrong subnet |
| Option E | Management VLAN interface is shutdown on SW4 |
| Option F | Answer : D Explanation: In the network, VLAN 300 is called the Management VLAN. Based on the configurations shown below, SW1 has VLAN 300 configured with the IP address of 192.168.10.1/24, while on SW4 VLAN 300 has an IP address of 192.168.100.4/24, which is not in the same subnet.
|
| Correct Answer | F |
