The exhibit shows both interfaces configured as dynamic auto but  status is trunking.

If both ports are dynamic auto the trunk would not come up and the command output of show interface trunk would not display any trunks.

IOU1#sh cdp ne
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
                  D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID        Local Intrfce    Holdtme    Capability  Platform  Port ID
IOU2            Eth 0/0          134            R S I  Linux Uni Eth 0/0

Total cdp entries displayed : 1
IOU1#sh run int e 0/0
Building configuration...

Current configuration : 29 bytes
!
interface Ethernet0/0
end

IOU1#show interface ethernet0/0 switchport | inc Administrative Mode:
Administrative Mode: dynamic auto
IOU1#sh int trunk
IOU1#

#############################################
IOU2#sho cdp ne
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
                  D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID        Local Intrfce    Holdtme    Capability  Platform  Port ID
IOU1            Eth 0/0          157            R S I  Linux Uni Eth 0/0

Total cdp entries displayed : 1
IOU2#sh run int e0/0
Building configuration...

Current configuration : 29 bytes
!
interface Ethernet0/0
end

IOU2#show interface ethernet0/0 switchport | inc Administrative Mode:
Administrative Mode: dynamic auto
IOU2#sh int trunk
IOU2#
IOU2#

Either of these answers will work depending on which switch the configurations are applied.

[*]Configure channel-group 1 mode desirable on both interfaces.
[*]Configure channel-group 1 mode active on both interfaces.

[*]configuring both interfaces of  switch3 for PAgP (desirable) would work
[*]configuring both interfaces of switch2 for LACP (active) would work

Can anyone recommend a suitable, (minimally priced, but adequate sim to use for ENCOR?

I believe this question is asking about bi-directional communication between LISP and NON-LISP Sites. 
The provided reference shows both PETR an PITR as requirements for LISP to NON-LISP connectivity.

A MR accepts LISP encapsulated map requests from an ITR


Proxy Ingress/Egress Tunnel Router (PxTR)
Sites cannot all be LISP enabled immediately, and not all segments of the network are not capable of running LISP from day 1. With the gradual migration from non-LISP-enabled sites to LISP-enabled sites, network operators still require that the non-LISP-capable sites be able to send traffic destined to LISP-enabled sites. This is where proxy ingress/egress tunnel routers (PxTRs) come into play.
Proxy ingress tunnel routers (PITRs) allow for non-LISP sites to send packets to LISP sites. A PITR is a new network element that shares many characteristics with a LISP ITR. A PITR allows non-LISP sites to send packets to LISP sites without requiring changes in the protocol or devices at the non-LISP sites. PITRs perform two primary functions:

• Originating EID advertisements: PITRs advertise highly aggregated EID-prefix space on behalf of LISP sites to the non-LISP sites so that the non-LISP sites can reach them.
  
• Encapsulating legacy Internet traffic: PITRs encapsulate non-LISP Internet traffic into LISP packets and route them toward their destination RLOCs.
  

• Avoiding strict uRPF failures: Some providers’ access networks require the source of a packet to be within the address scope of the access networks. PETRs allow for LISP sites to send packets to non-LISP sites in cases where the access network does not allow for the LISP site to send packets with the source address of the site’s EIDs.
  
• Traversing a different IP protocol: The transit path network between LISP sites and non-LISP sites may not be IPv4 or IPv6 enabled. LISP support for mixed protocol encapsulation allows PETRs to hop over such networks in order to route the traffic between the LISP and non-LISP sites.
  

Correct answers are

Remove all configuration related to crypto map from R1 and R2 and eliminate the ACL.
Create an IPsec profile, associate the transform-set, and apply the profile to the tunnel interface.

https://www.youtube.com/watch?v=A6UoUOsbWuk


https://www.cisco.com/c/en/us/td/docs/io...F46CFDD07B

Correct answers are

PE1 will reject the route due to automatic route filtering.
After you configure route-target import 999:999 for a VRF on PE1, the route will be accepted.


The below option is incorrect.
After you configure route-target import 999:999 for a VRF on PE3, the route will be accepted

You would not import the VRF router target on R3,  The VRF was created on R3.

What purpose does a trunk use? It is only needed if both host devices are on separate VLANs.  But the question specifically states L3  connectivity.  Why not just use a virtual switch?

https://vdc-repo.vmware.com/vmwb-reposit....11.4.html

The wireless LAN Controller is embedded into the access point is the correct answer.

In a Cisco Mobility Express network, Access Point (AP) running the wireless controller function is designated as the primary AP. The other Access Points which are managed by this primary AP are referred as Subordinate APs.
The primary AP has two roles:

1. It functions and operates as a wireless LAN controller to manage and control the Subordinate APs. The Subordinate APs operates as lightweight access points to serve clients.
   
2. Primary AP operates as an Access Point to serve clients.
   

The exhibit is incorrect.  Ports on both switches are

Administrative Mode: dynamic Auto
Operational Mode: trunk

Dynamic auto on both sides will not form a trunk.

This misleads me to think I do not need to change a setting since the trunk is formed.

Hello all,
1. Thanks for the website
2. Could you please review AN604 on the automation and programmability section. I'm not sure if that is the correct answer after doing some research. Could you guys please elaborate on how it is Representational State Transfer Application Programming Interface and not Application Programming Interface
Thanks for the help/ confirmation.