Cisco 200-301 Exam Dumps, Practice Test Questions

Router A’s physical address is not the HSRP virtual identity and becomes unusable after failure.

Although Router B transmits its own frames with its physical address, hosts use the HSRP virtual MAC as their default-gateway destination.

Broadcast Ethernet is used for some discovery traffic such as ARP requests, not the destination MAC for every routed unicast packet.

Marking the user-facing LAN as outside reverses the intended NAT direction and does not designate inside hosts as the source network.

Static inside-source translations are configured in global mode; the requirement here is interface classification, not a one-to-one mapping.

The show command is read-only operational verification and does not mark an interface as a NAT inside boundary.

Marking both edges as inside would not identify the WAN as the external NAT-facing direction needed for inside-source translation.

Statistics report counters and pool state but do not label the physical WAN interface for NAT operation.

The overload translation policy is configured globally; it does not replace the required interface-level outside designation.

PAT overload shares one interface IP across many sessions; it does not reserve one stable 203.0.113.20 identity for 10.10.1.20.

Outside-source NAT translates the other direction of address role and is not the requested inside-source host mapping.

The inside address differs from the named internal host and would map a different device.

Aggregate counters summarize use but do not list the individual inside-local/inside-global tuple entries requested.

The routing table contains prefixes and next hops rather than active NAT translation mappings.

An ACL may select NAT candidates but does not display every active inside/outside mapping.

That can show individual translations, but show ip nat statistics directly provides the aggregate hit/miss and pool summary requested.

Physical interface counters do not expose NAT pool utilization and translation statistics.

Installed route information does not describe NAT allocation pool and hit/miss counters.

The ending address .120 exceeds the approved .105 pool boundary.

A static inside-source mapping is not the six-address named allocation pool required here.

A /29 mask does not correctly describe the specified source /24 global allocation and would not preserve the requested pool context.

The selection ACL should match inside-local 10.10.1.0/24 addresses, not addresses allocated after NAT.

That would select many internal hosts beyond the authorized 10.10.1.0/24 and violate the restriction.

The standard ACL for inside-source NAT should identify eligible source addresses, not substitute a destination wildcard.

That is PAT through a single outside interface address, not dynamic 1:1 use of named pool OUTSIDE.

A single static host mapping would not dynamically allocate outside addresses to all hosts selected by ACL 10.

Defining a pool is not sufficient; the inside source ACL must be bound to the pool by the mapping rule.

This reverses the stated trusted LAN versus ISP directions for the inside-source NAT policy.

The ISP-facing side must be identified as outside, not another inside interface.

The mapping rule alone does not define which routed interfaces participate as NAT inside and outside.

Dynamic pool NAT without overloading assigns global address translations but does not explicitly reuse one interface address with transport-port multiplexing.

A static one-to-one mapping binds one inside host to one global address and does not supply generalized PAT for many users.

Removing the inside role would prevent normal inside-source NAT for that LAN, not enable shared overload.