Answer: A 

Explanation: 

Extended Unique Identifier (EUI), as per RFC2373, allows a host to assign iteslf a unique 64-

Bit IP Version 6 interface identifier (EUI-64). This feature is a key benefit over IPv4 as it eliminates the

need of manual configuration or DHCP as in the world of IPv4. The IPv6 EUI-64 format address is obtained

through the 48-bit MAC address. The Mac address is first separated into two 24-bits, with one being OUI

(Organizationally Unique Identifier) and the other being NIC specific. The 16-bit 0xFFFE is then inserted

between these two 24-bits to for the 64-bit EUI address. IEEE has chosen FFFE as a reserved value which

can only appear in EUI-64 generated from the an EUI-48 MAC address. Here is an example showing how

a the Mac Address is used to generate EUI.

Next, the seventh bit from the left, or the universal/local (U/L) bit, needs to be inverted. This bit identifies whether this interface identifier is universally or locally administered. If 0, the address is locally

administered and if 1, the address is globally unique. It is worth noticing that in the OUI portion, the globally

unique addresses assigned by the IEEE has always been set to 0 whereas the locally created addresses

has 1 configured. Therefore, when the bit is inverted, it maintains its original scope (global unique address

is still global unique and vice versa). The reason for inverting can be found in RFC4291 section 2.5.1.

Once the above is done, we have a fully functional EUI-64 format address. 

Reference: https://

supportforums.cisco.com/document/100566/understanding-ipv6-eui-64-bit- address

Answer: A 

Explanation: 

To enable the exporting of information in NetFlow cache entries, use the ip flow-export destination

command in global configuration mode.

Syntax Description

ip- IP address of the workstation to which you want to send the address NetFlow information.

udp-port UDP protocol-specific port number.

Reference:

http://www.cisco.com/c/en/us/td/docs/ios/12_0s/feature/guide/12s_mdnf.html#wp1023091

Answer: D 

Explanation: 

Configuring NAT to Allow Internal Users to Access the Internet Using Overloading NAT Router

interface ethernet 0

ip address 10.10.10.1 255.255.255.0

ip nat inside

!--- Defines Ethernet 0 with an IP address and as a NAT inside interface.

interface ethernet 1

ip address 10.10.20.1 255.255.255.0

ip nat inside

!--- Defines Ethernet 1 with an IP address and as a NAT inside interface.

interface serial 0

ip address 172.16.10.64 255.255.255.0

ip nat outside

!--- Defines serial 0 with an IP address and as a NAT outside interface.

ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 24 !

!--- Defines a NAT pool named ovrld with a range of a single IP

!--- address, 172.16.10.1.

ip nat inside source list 7 pool ovrld overload

!

!

!

!

!--- Indicates that any packets received on the inside interface that

!--- are permitted by access-list 7 has the source

address

!--- translated to an address out of the NAT pool named ovrld.

!--- Translations are overloaded, which allows multiple inside

!--- devices to be translated to the same valid IP

address.

access-list 7 permit 10.10.10.0 0.0.0.31

access-list 7 permit 10.10.20.0 0.0.0.31

!--- Access-list 7 permits packets with source addresses ranging from

!--- 10.10.10.0 through 10.10.10.31 and 10.10.20.0

through 10.10.20.31.

Note in the previous second configuration, the NAT pool "ovrld"only has a range of one address. The

keyword overload used in the ip nat inside source list 7 pool

ovrld overload command allows NAT to translate multiple inside devices to the single address in the pool.

Reference:

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080094e77.shtml

Answer: D 

Explanation: 

show ipv6 traffic Field Descriptions

Field Description

source- Number of source-routed packets.

routed

truncated Number of truncated packets.

format Errors that can result from checks performed on header fields, errors the version number, and

packet length.

not a Message sent when IPv6 unicast routing is not enabled.

router

Reference:

http://www.cisco.com/c/en/us/td/docs/ios/ipv6/command/reference/ipv6_book/ipv6_16.html

Answer: A 

Explanation: 

Answer: A,B 

Explanation: 

Network Address Translation IPv6 to IPv4, or NAT64, technology facilitates communication

between IPv6-only and IPv4-only hosts and networks (whether in a transit, an access, or an edge

network). This solution allows both enterprises and ISPs to accelerate IPv6 adoption while simultaneously

handling IPv4 address depletion. The DNS64 and NAT64 functions are completely separated, which is

essential to the superiority of NAT64 over NAT-PT. Reference: http:// www.cisco.com/c/en/us/products/

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

Answer: B 

Explanation: 

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

Answer: D 

Explanation: 

Access list 2 is more specific, allowing only 1.2.3.0/24, whereas access list 1 permits all 1.0.0.0/8

networks. This question also asks us to apply this distribute list only to the outbound direction of the fast Ethernet 0/0 interface, so the correct command is "distribute list 2

out FastEthernet0/0."

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