200-301 無料問題集「Cisco Certified Network Associate」
Drag and drop the characteristics of northbound APIs from the left onto any position on the right. Not all characteristics are used.
正解：
Explanation:
Cisco CCNA 200-301 v1.1 Network Fundamentals questions of this form test whether each protocol, command, service, or architecture term is placed with the function it actually performs. The safest approach is to classify each item by operating layer and purpose before matching it: routing behavior belongs to IP connectivity, wireless modes belong to access, REST methods belong to automation, and AAA functions belong to security services. Several distractors are valid networking terms, but they become wrong when mapped to the wrong plane or protocol. The retained mapping follows Cisco terminology and reflects how the features are used in implementation and troubleshooting. In practice, this prevents mixing up forwarding behavior with management behavior or authentication with authorization/accounting. The mapping shown in the file is therefore retained as the verified response.
Drag and drop the HTTP methods used with REST-Based APIs from the left onto the descriptions on the right.
正解：
Explanation:
Cisco CCNA 200-301 v1.1 Network Fundamentals questions of this type test whether each item is matched to the technology that actually performs that role. The reliable method is to classify each term by operating layer, packet behavior, management function, or security purpose before matching it. Several terms in these items are legitimate Cisco networking concepts, but they become wrong when assigned to the wrong protocol or plane. The mapping retained in the document follows that separation: transport behavior is matched to TCP or UDP, wireless or security terms are matched to their mechanisms, and automation items are matched to the correct API or management model. This matters operationally because troubleshooting fails quickly when a forwarding-plane function is treated as a management-plane feature or when a security control is applied to the wrong threat. The shown mapping is therefore retained as the verified response.
Configure IPv4 and IPv6 connectivity between two routers. For IPv4, use a /28 network from the 192.168.1.0
/24 private range. For IPv6, use the first /64 subnet from the 2001:0db8:aaaa::/48 subnet.
1. Using Ethernet0/1 on routers R1 and R2, configure the next usable/28 from the 192.168.1.0/24 range. The network 192.168.1.0/28 is unavailable.
2. For the IPv4 /28 subnet, router R1 must be configured with the first usable host address.
3. For the IPv4 /28 subnet, router R2 must be configured with the last usable host address.
4. For the IPv6 /64 subnet, configure the routers with the IP addressing provided from the topology.
5. A ping must work between the routers on the IPv4 and IPv6 address ranges.
/24 private range. For IPv6, use the first /64 subnet from the 2001:0db8:aaaa::/48 subnet.
1. Using Ethernet0/1 on routers R1 and R2, configure the next usable/28 from the 192.168.1.0/24 range. The network 192.168.1.0/28 is unavailable.
2. For the IPv4 /28 subnet, router R1 must be configured with the first usable host address.
3. For the IPv4 /28 subnet, router R2 must be configured with the last usable host address.
4. For the IPv6 /64 subnet, configure the routers with the IP addressing provided from the topology.
5. A ping must work between the routers on the IPv4 and IPv6 address ranges.
正解：
See the Explanation below.
Explanation:
Answer as below configuration:
on R1
config terminal
ipv6 unicast-routing
inter eth0/1
ip addre 192.168.1.1 255.255.255.240
ipv6 addre 2001:db8:aaaa::1/64
not shut
end
copy running start
on R2
config terminal
ipv6 unicast-routing
inter eth0/1
ip address 192.168.1.14 255.255.255.240
ipv6 address 2001:db8:aaaa::2/64
not shut
end
copy running start
---------------------
for test from R1
ping ipv6 2001:db8:aaaa::1
for test from R2
ping ipv6 2001:db8:aaaa::2
Explanation:
Answer as below configuration:
on R1
config terminal
ipv6 unicast-routing
inter eth0/1
ip addre 192.168.1.1 255.255.255.240
ipv6 addre 2001:db8:aaaa::1/64
not shut
end
copy running start
on R2
config terminal
ipv6 unicast-routing
inter eth0/1
ip address 192.168.1.14 255.255.255.240
ipv6 address 2001:db8:aaaa::2/64
not shut
end
copy running start
---------------------
for test from R1
ping ipv6 2001:db8:aaaa::1
for test from R2
ping ipv6 2001:db8:aaaa::2
