Refined of 300-101 practice test materials and study guides for Cisco certification for IT candidates, Real Success Guaranteed with Updated 300-101 pdf dumps vce Materials. 100% PASS Implementing Cisco IP Routing exam Today!

2017 Apr 300-101 free exam questions

Q51. For security purposes, an IPv6 traffic filter was configured under various interfaces on the local router. However, shortly after implementing the traffic filter, OSPFv3 neighbor adjacencies were lost. What caused this issue? 

A. The traffic filter is blocking all ICMPv6 traffic. 

B. The global anycast address must be added to the traffic filter to allow OSPFv3 to work properly. 

C. The link-local addresses that were used by OSPFv3 were explicitly denied, which caused the neighbor relationships to fail. 

D. IPv6 traffic filtering can be implemented only on SVIs. 

Answer:

Explanation: 

OSPFv3 uses link-local IPv6 addresses for neighbor discovery and other features, so if any IPv6 traffic

filters are implemented be sure to include the link local address so that it is permitted in the filter list.

Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx- os/unicast/configuration/

guide/l3_cli_nxos/l3_ospfv3.html


Q52. A network engineer executes the show ip flow export command. Which line in the output indicates that the send queue is full and export packets are not being sent? 

A. output drops 

B. enqueuing for the RP 

C. fragmentation failures 

D. adjacency issues 

Answer:

Explanation: 

Table 5 show ip flow export Field Descriptions Field Description Exporting flows to 10.1.1.1

Specifies the export destinations and ports. (1000) and 10.2.1.1 The ports are in parentheses. Exporting

using source Specifies the source address or interface. IP address 10.3.1.1 Version 5 flow records

Specifies the version of the flow. 11 flows exported in 8 udp The total number of export packets sent, and

datagrams the total number of flows contained within them. 0 flows failed due to lack of No memory was

available to create an export export packet packet. 0 export packets were sent The packet could not be

processed by CEF or up to process level by fast switching, possibly because another feature requires

running on the packet. 0 export packets were Indicates that CEF was unable to switch the dropped due to

no fib packet or forward it up to the process level. 0 export packets were dropped due to adjacency issues

0 export packets were Indicates that the packet was dropped because dropped due to of problems

constructing the IP packet. fragmentation failures 0 export packets were dropped due to encapsulation

fixup failures 0 export packets were Indicates that there was a problem transferring dropped enqueuing for

the the export packet between the RP and the line RP card. 0 export packets were dropped due to IPC

rate limiting 0 export packets were Indicates that the send queue was full while dropped due to output the

packet was being transmitted. drops

Reference: http://www.cisco.com/c/en/us/td/docs/ios/12_0s/feature/guide/oaggnf.html


Q53. For troubleshooting purposes, which method can you use in combination with the “debug ip packet” command to limit the amount of output data? 

A. You can disable the IP route cache globally. 

B. You can use the KRON scheduler. 

C. You can use an extended access list. 

D. You can use an IOS parser. 

E. You can use the RITE traffic exporter. 

Answer:

Explanation: 

The debug ip packet command generates a substantial amount of output and uses a substantial amount of

system resources. This command should be used with caution in production networks. Always use with the access-list command to apply an extended ACL to the debug output. Reference: http://www.cisco.com/c/en/us/support/docs/security/dynamic-multipoint-vpn-dmvpn/111976-dmvpn-troubleshoot-00.html


Q54. Which three characteristics are shared by subinterfaces and associated EVNs? (Choose three.) 

A. IP address 

B. routing table 

C. forwarding table 

D. access control lists 

E. NetFlow configuration 

Answer: A,B,C 

Explanation: 

A trunk interface can carry traffic for multiple EVNs. To simplify the configuration process, all

the subinterfaces and associated EVNs have the same IP address assigned. In other words, the trunk

interface is identified by the same IP address in different EVN contexts. This is accomplished as a result of

each EVN having a unique routing and forwarding table, thereby enabling support for overlapping IP

addresses across multiple EVNs. Reference: http://www.cisco.com/en/US/docs/ios-xml/ios/evn/

configuration/xe-3sg/evn- overview.pdf


Q55. You have been asked to evaluate how EIGRP is functioning in a customer network. 

What is the advertised distance for the 192.168.46.0 network on R1? 

A. 333056 

B. 1938688 

C. 1810944 

D. 307456 

Answer:

Explanation: 


Improve 300-101 exam topics:

Q56. Refer to the following output: 

Router#show ip nhrp detail 

10.1.1.2/8 via 10.2.1.2, Tunnel1 created 00:00:12, expire 01:59:47 

TypE. dynamic, Flags: authoritative unique nat registered used 

NBMA address: 10.12.1.2 

What does the authoritative flag mean in regards to the NHRP information? 

A. It was obtained directly from the next-hop server. 

B. Data packets are process switches for this mapping entry. 

C. NHRP mapping is for networks that are local to this router. 

D. The mapping entry was created in response to an NHRP registration request. 

E. The NHRP mapping entry cannot be overwritten. 

Answer:

Explanation: 

Show NHRP: Examples

The following is sample output from the show ip nhrp command:

Router# show ip nhrp

10.0.0.2 255.255.255.255, tunnel 100 created 0:00:43 expire 1:59:16 Type: dynamic Flags: authoritative

NBMA address: 10.1111.1111.1111.1111.1111.1111.1111.1111.1111.11 10.0.0.1 255.255.255.255,

Tunnel0 created 0:10:03 expire 1:49:56 Type: static Flags: authoritative NBMA address: 10.1.1.2 The

fields in the sample display are as follows:

The IP address and its network mask in the IP-to-NBMA address cache. The mask is always

255.255.255.255 because Cisco does not support aggregation of NBMA information through NHRP.

The interface type and number and how long ago it was created (hours:minutes:seconds).

The time in which the positive and negative authoritative NBMA address will expire

(hours:minutes:seconds). This value is based on the ip nhrp holdtime

command.

Type of interface:

dynamic--NBMA address was obtained from the NHRP Request packet.

static--NBMA address was statically configured.

Flags:

authoritative--Indicates that the NHRP information was obtained from the Next Hop Server or router that

maintains the NBMA-to-IP address mapping for a particular destination. Reference: http://www.cisco.com/

c/en/us/td/docs/ios/12_4/ip_addr/configuration/guide/hadnhrp.html


Q57. A packet capture log indicates that several router solicitation messages were sent from a local host on the IPv6 segment. What is the expected acknowledgment and its usage? 

A. Router acknowledgment messages will be forwarded upstream, where the DHCP server will allocate addresses to the local host. 

B. Routers on the IPv6 segment will respond with an advertisement that provides an external path from the local subnet, as well as certain data, such as prefix discovery. 

C. Duplicate Address Detection will determine if any other local host is using the same IPv6 address for communication with the IPv6 routers on the segment. 

D. All local host traffic will be redirected to the router with the lowest ICMPv6 signature, which is statically defined by the network administrator. 

Answer:

Explanation: 

Router Advertisements (RA) are sent in response to router solicitation messages. Router

solicitation messages, which have a value of 133 in the Type field of the ICMP packet header, are sent by

hosts at system startup so that the host can immediately autoconfigure without needing to wait for the next

scheduled RA message. Given that router solicitation messages are usually sent by hosts at system

startup (the host does not have a configured unicast address), the source address in router solicitation

messages is usually the unspecified IPv6 address (0:0:0:0:0:0:0:0). If the host has a configured unicast

address, the unicast address of the interface sending the router solicitation message is used as the source

address in the message. The destination address in router solicitation messages is the all-routers multicast

address with a scope of the link. When an RA is sent in response to a router solicitation, the destination

address in the RA message is the unicast address of the source of the router solicitation message. RA

messages typically include the following information:

One or more onlink IPv6 prefixes that nodes on the local link can use to automatically configure their IPv6

addresses

Lifetime information for each prefix included in the advertisement

Sets of flags that indicate the type of autoconfiguration (stateless or stateful) that can be completed

Default router information (whether the router sending the advertisement should be used as a default

router and, if so, the amount of time (in seconds) the router should be used as a default router)

Additional information for hosts, such as the hop limit and MTU a host should use in packets that it

originates Reference: http://www.cisco.com/c/en/us/td/docs/ios/ipv6/configuration/guide/12_4t/

ipv6_12_4t_book/ip6- addrg_bsc_con.html


Q58. Which two methods of deployment can you use when implementing NAT64? (Choose two.) 

A. stateless 

B. stateful 

C. manual 

D. automatic 

E. static 

F. functional 

G. dynamic 

Answer: A,B 

Explanation: 

While stateful and stateless NAT64 perform the task of translating IPv4 packets into IPv6 packets and vice

versa, there are important differences. The following

table provides a high-level overview of the most relevant differences.

Table 2. Differences Between Stateless NAT64 and Stateful NAT64

Stateless NAT64 Stateful NAT64

1:1 translation 1:N translation

No conservation of IPv4 address Conserves IPv4 address

Assures end-to-end address Uses address overloading, hence transparency and scalability lacks in endto-

end address transparency

No state or bindings created on the State or bindings are created on every translation unique translation

Requires IPv4-translatable IPv6 No requirement on the nature of IPv6 addresses assignment (mandatory

address assignment requirement)

Requires either manual or DHCPv6 Free to choose any mode of IPv6 based address assignment for IPv6

address assignment viz. Manual, hosts DHCPv6, SLAAC Reference: http://www.cisco.com/c/en/us/

products/collateral/ios-nx-os-software/enterprise-ipv6- solution/white_paper_c11-676277.html


Q59. You have been asked to evaluate how EIGRP is functioning in a customer network. 

Which key chain is being used for authentication of EIGRP adjacency between R4 and R2? 

A. CISCO 

B. EIGRP 

C. key 

D. MD5 

Answer:

Explanation: R4 and R2 configs are as shown below: 

Clearly we see the actual key chain is named CISCO. 


Q60. Which two actions must you perform to enable and use window scaling on a router? (Choose two.) 

A. Execute the command ip tcp window-size 65536. 

B. Set window scaling to be used on the remote host. 

C. Execute the command ip tcp queuemax. 

D. Set TCP options to "enabled" on the remote host. 

E. Execute the command ip tcp adjust-mss. 

Answer: A,B 

Explanation: 

The TCP Window Scaling feature adds support for the Window Scaling option in RFC 1323,

TCP Extensions for High Performance . A larger window size is recommended to improve TCP performance in network paths with large bandwidth-delay product characteristics that are called Long Fat

Networks (LFNs). 

The TCP Window Scaling enhancement provides that support. The window scaling extension in Cisco IOS software expands the definition of the TCP window to 32 bits and then uses a scale factor to carry this 32-bit value in the 16-bit window field of the TCP header. 

The window size can increase to a scale factor of 14. Typical applications use a scale factor of 3 when deployed in LFNs. 

The TCP Window Scaling feature complies with RFC 1323. The larger scalable window size will allow TCP to perform better over LFNs. 

Use the ip tcp window-size command in global configuration mode to configure the TCP window size. In order for this to work, the remote host must also support this feature and its window size must be increased. 

Reference: http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipapp/

configuration/12-4t/iap-12- 4t-book/iap-tcp.html#GUID-BD998AC6-F128-47DD-B5F7-B226546D4B08