Cisco (300-410-ENARSI) Exam Questions And Answers page 27

Any IP SLA operations accuracy can be enhanced by configure an IP SLA responder on the destination device. It is important to note that only Cisco devices support the configuration as a responder.
You do not configure an IP SLA responder on the source device. You schedule the operation on the source device and the destination device is the one that is configured as a responder.
You do not schedule the operation on the destination device. You schedule the operation on the source device and the destination device is the one that is configured as a responder.
Adding the verify-data command to the configuration of the operation will not enhance the accuracy of the information gathered. When data verification is enabled, each operation response is checked for corruption. Use the verify-data command with caution during normal operations because it generates unnecessary overhead.
Objective:
Infrastructure Services
Sub-Objective:
Configure and verify IP SLA
IP SLAs Configuration Guide, Cisco IOS Release 15M > Configuring IP SLAs TCP Connect Operations

The configuration indicates all steps are complete except for globally enabling IPv6 routing. If that had been done, the configuration output would have reflected it under the interface as follows:
interface S0/0/1
ipv6 address 2001:610:FFFF:1::1/64
ipv6 ospf 100 area 0
ipv6 enable
ipv6 router ospf 100
router-id 10.1.1.6

Prior to configuring OSPFv3 on an interface, it must be enabled globally. OSPFv3 is an OSPF version specific to IPv6. The following commands will globally enable OSPF v3. It will then be reflected by the ipv6 enable statement under the interface when viewing the configuration as shown in the fourth line of the output above.
Router5(config)# ipv6 unicast-routing
Router5(config)# ipv6 ospf 100
Router5(config-rtr)# router-id 10.1.1.6

The problem is not the router ID. The configuration in the scenario does assign a router ID, as indicated by these lines:
ipv6 router ospf 100
router-id 10.1.1.6

The problem is not the IPv6 address. The configuration does assign an IPv6 address to the interface, as indicated by these lines:
interface S0/0/1
ipv6 address2001:610:FFFF:1::1/64

OSPF area 0 is not the problem. The configuration does place the interface in OSPF area 0, as indicated by these lines:
interface S0/0/1
ipv6 ospf 100 area 0

Objective:
Layer 3 Technologies
Sub-Objective:
Configure and verify OSPF for IPv6
Cisco > Implementing OSPF for IPv6 > How to Implement OSPF for IPv6

It provides neither authentication nor encryption. In SNMPv3 there are three combinations of security that can be used:
noAuthNoPriv- no authentication and no encryption noauth keyword in the configuration
AuthNoPriv - messages are authenticated but not encrypted auth keyword in the configuration
AuthPriv - messages are authenticated and encrypted priv keyword in the configuration
In this case, the keyword noauth in the configuration indicates that no authentication and no encryption are provided. This makes the implementation no more secure than SNMPv1 or SNMPv2.
In SNMPv1 and SNMPv2, authentication is performed using a community string. When you implement SNMP using the noauth keyword, it does not use community strings for authentication. Instead it uses the configured user or group name (in this case NORMAL). Regardless, it does not provide either authentication or encryption.
Objective:
Infrastructure Services
Sub-Objective:
Configure and verify SNMP
SNMP Configuration Guide, Cisco IOS XE Release 3SE (Catalyst 3850 Switches) > SNMPv3

Stateless NAT64 does not support translating from the IPv6 Internet to an IPv4 network. NAT64 is a version of network address translation that translates IPv6 address to IPv4 and vice versa. It has two variants, stateless and stateful. In stateless translation, mappings are created using an algorithm, but those mappings are not maintained while translation is being performed. Stateful NAT64 both creates and maintains mappings during translation.
Due to the fact it does not maintain mappings, stateless NAT64 supports all of the options given except translating from the IPv6 Internet to an IPv4 network.
Objective:
Infrastructure Services
Sub-Objective:
Describe IPv6 NAT
Home > Products & services > Cisco IOS and NX-OS software > Cisco IOS technologies > Enterprise ipv6 solution > Data sheets and literature > White papers > NAT64 Technology: Connecting IPv6 and IPv4 Networks > Technologies Facilitating IPv6/IPv4 Translation

DNS64 and NAT64 functions are completely separated when using NAT64. In NAT-PT these two functions are tightly coupled, which reduces flexibility and is why NAT-PT has been deprecated, with the IETF proposing NAT64 as its viable successor.
DNS64 and NAT64 functions are not completely integrated in NAT64, so this is not an advantage of NAT64 over NAT-PT as a translation option.
NAT64 works over non- Ethernet networks. It is NAT-PT that does only works on Ethernet networks. Therefore, this is not an advantage of NAT 64 over NAT-PT.
NAT64 can reconstruct fragments packets if they are fragmented by an intermediate IPv4 router. It is NAT-PT that will be unable to reconstruct fragments packets if they are fragmented by an intermediate IPv4 router, so this is not an advantage of NAT 64 over NAT-PT.
Objective:
Infrastructure Services
Sub-Objective:
Describe IPv6 NAT
Home > Products & services > Cisco IOS and NX-OS software > Cisco IOS technologies > Enterprise IPv6 solution > Data sheets and literature > White papers > NAT64 Technology: Connecting IPv6 and IPv4 Networks > Technologies Facilitating IPv6/IPv4 Translation

One of the characteristics of stateful NAT64 is that it conserves IPv4 addresses. NAT64 is a version of network address translation that translates IPv6 address to IPv4 and vice versa. It has two variants, stateless and stateful. The following table describes some of the major differences between the two:

NAT64 has neither the variant static nor the variant manual.
Objective:
Infrastructure Services
Sub-Objective:
Describe IPv6 NAT
Home > Products & services > Cisco IOS and NX-OS software > Cisco IOS technologies > Enterprise ipv6 solution > Data sheets and literature > White papers > NAT64 Technology: Connecting IPv6 and IPv4 Networks > Technologies Facilitating IPv6/IPv4 Translation