10 Tips For Avant-garde 300-101 practice test

Answer: A 

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

Answer: B 

Explanation: 

A new interface configuration command, dialer persistent, allows a dial-on-demand routing (DDR) dialer

profile connection to be brought up without being triggered by interesting traffic. When configured, the dialer persistent command starts a timer when the dialer interface starts up and starts the connection when the timer expires. If interesting traffic arrives before the timer expires, the connection is still brought up and set as persistent. The command provides a default timer interval, or you can set a custom timer interval. To configure a dialer interface as persistent, use the following commands beginning in global configuration mode:

Command Purpose

Step 1 Router(config)# interface dialer Creates a dialer interface and number enters interface

Configuration mode.

Step 2 Router(config-if)# ip address Specifies the IP address and mask address mask of the dialer

interface as a node in the destination network to be called.

Step 3 Router(config-if)# encapsulation Specifies the encapsulation type.

type

Step 4 Router(config-if)# dialer string Specifies the remote destination to dial-string class class-name call

and the map class that defines characteristics for calls to this destination.

Step 5 Router(config-if)# dialer pool Specifies the dialing pool to use number for calls to this destination.

Step 6 Router(config-if)# dialer-group Assigns the dialer interface to a group-number dialer group.

Step 7 Router(config-if)# dialer-list Specifies an access list by list dialer-group protocol protocol- number or

by protocol and list name {permit | deny | list number to define the interesting access-list-number} packets that can trigger a call. Step 8 Router(config-if)# dialer

(Optional) Specifies the remote-name user-name

authentication name of the remote router on the destination subnetwork for a dialer interface.

Step 9 Router(config-if)# dialer Forces a dialer interface to be persistent [delay [initial] connected at all

times, even in seconds | max-attempts the absence of interesting traffic.

number]

Reference:

http://www.cisco.com/c/en/us/td/docs/ios/dial/configuration/guide/12_4t/dia_12_4t_book/dia_dia

ler_persist.html

Answer: C 

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

Answer: A 

Explanation: 

Dynamic address mapping uses Frame Relay Inverse ARP to request the next-hop protocol address for a

specific connection, given its known DLCI. Responses to

Inverse ARP requests are entered in an address-to-DLCI mapping table on the router or access server; the

table is then used to supply the next-hop protocol

address or the DLCI for outgoing traffic.

Reference:

http://www.cisco.com/c/en/us/td/docs/ios/12_2/wan/configuration/guide/fwan_c/wcffrely.html

Answer: D 

Explanation: 

With PPPoE, the two authentication options are PAP and CHAP. When CHAP is enabled on

an interface and a remote device attempts to connect to it, the access server sends a CHAP packet to the

remote device. The CHAP packet requests or "challenges" the remote device to respond. The challenge

packet consists of an ID, a random number, and the host name of the local router. When the remote device

receives the challenge packet, it concatenates the ID, the remote device's password, and the random

number, and then encrypts all of it using the remote device's password. The remote device sends the

results back to the access server, along with the name associated with the password used in the

encryption process. When the access server receives the response, it uses the name it received to retrieve

a password stored in its user database. The retrieved password should be the same password the remote

device used in its encryption process. The access server then encrypts the concatenated information with

the newly retrieved password--if the result matches the result sent in the response packet, authentication

succeeds. The benefit of using CHAP authentication is that the remote device's password is never

transmitted in clear text (encrypted). This prevents other devices from stealing it and gaining illegal access

to the ISP's network. Reference: http://www.cisco.com/c/en/us/td/docs/ios/12_2/security/configuration/

guide/fsecur_c/scfathen.ht ml

Answer: A 

Explanation: 

The standby track command allows you to specify another interface on the router for the

HSRP process to monitor in order to alter the HSRP priority for a given group. If the line protocol of the

specified interface goes down, the HSRP priority is reduced. This means that another HSRP router with

higher priority can become the active router if that router has standby preempt enabled. Loopback

interfaces can be tracked, so when this interface is shut down the HSRP priority for that router will be

lowered and the other HSRP router will then become the active one. Reference: http://www.cisco.com/c/

en/us/support/docs/ip/hot-standby-router-protocol- hsrp/13780-6.html

Answer: B 

Explanation: 

Answer: D 

Explanation: 

PAP authentication involves a two-way handshake where the username and password are

sent across the link in clear text; hence, PAP authentication does not provide any protection against

playback and line sniffing. CHAP authentication, on the other hand, periodically verifies the identity of the

remote node using a three-way handshake. After the PPP link is established, the host sends a "challenge"

message to the remote node. The remote node responds with a value calculated using a one-way hash

function. The host checks the response against its own calculation of the expected hash value. If the

values match, the authentication is acknowledged; otherwise, the connection is terminated. Reference:

http://www.cisco.com/c/en/us/support/docs/wan/point-to-point-protocol-ppp/10241- ppp-callinhostname.

html

Answer: C 

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

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