routemap

@pipeYes still valid. take it

pls update

Up

Up! Thanks!

pls share

Great

pls reupload thanks

New updates on Design exam please share thanks

Hi @Jocantaro, may I know your thoughts on this question below? Question 35: Which are the characteristics of the different scripting method? (For every scripting method, select all characteristics that apply.) Columns: EEM Python, EEM Applet calling a standard Python script, Standard Python script without EEM 1. Requires Guestshell - (EEM Python, EEM Applet, Standard Python) Note: it seems Standard Python is included. [Hidden Content] 2. Allows sharing the same Python script for periodic and triggered collection - (EEM applet) 3. Allow scheduling a periodic collection run - (all) 4. Allow triggering the collection run on a BGP session event - (EEM Python, EEM Applet) 5.Allows running the Python script manually outside EEM (Standard Python)

Yes you're right on the LDP advertisement filter which applies for the next Question 18. Also had it tested before so I agree with E as the answer. What mechanism and type of deployment would be the most appropriate to accomplish the label filtering goals as requested? a) OSPF Prefix Suppression enabled globally on PE and P routers b) OSPF Prefix Suppression enabled on the IT Training Departments 200 loopback interfaces c) OSPF Prefix Suppression enabled on the links between PE and P routers d) LDP advertisement filter applied to P routers e) LDP advertisement filter applied to PE and P routers

@JocantaroThanks a lot this makes sense. I'll make my questions one by one so that this thread is active rather than putting it all at the same time. Hope others join the discussion. For the question below, your answer was B. Can you share your thoughts once again, or anyone who's reading this thread. -However I think A is the answer since on my testing, the infrastructure links should be MPLS-enabled. When I removed the 'mpls ip' configuration on the P2P links, the connection between the 2 sites (for example) was disconnected. -D also has the MPLS enabled for infrastructure links however the Loopback in P routers are not necessary for MPLS L3VPN. Question 17: What prefixes, along with their label bindings must be advertised by LDP in the MPLS mock lab to enable MPLS L3VPN services? a) Loopback0 prefixes of all PE routers and prefixes of all infrastructure links b) Loopback0 prefixes of all PE and P Routers c) Loopback0 prefixes of all PE routers d) Loopback0 prefixes of all PE and P routers, and prefixes of all infrastructure links

@Jocantaro Hello for item 14, may I ask how did you come up with the answer D and G? From my understanding the Administratively scoped block (239.0.0.0/8) can be used under RFC 2365.. But in the choices there are 4 items under that block. So c, d, f and g. Letter F cannot be the answer since the RapidStreaming will co-exist with JustStreaming for a while. So now the answers will fall on c, d, and g. Hope you can share your thoughts, thanks. Which two addresses are the best choices for the Connected FABD2 and RapidStreaming multicast groups? (Choose two.) a) 232.2.1.1 b) 232.1.1.1 c) 239.129.1.2 d) 239.2.1.1 e) 232.129.1.1 f) 239.1.1.2 g) 239.1.1.1

Yes that also works. The simplest solution would be the unique RDs from the choices provided as the others (A, D, E) are not reasonable.

Question 13: I think the best answer is "B". Technically it should be a combination of unique RD's and multipath. Unique RD configured on both PEs R5 & R6. And multipath configured in R4 (PE router) under VRF fabd2. Since the RD (100000) is the same on all PEs, when the Branch3 prefix gets sent to the RR, it only reflects the best path to the RR clients, so only 1 of the prefix is advertised. If the RDs are unique then both prefixes will be advertised. b) On r5 and r6, unique RDs need to be configured c) On r3 as the route reflector, BGP Multipath feature must be enabled --> C is incorrect as the multipath should be configured on the PE, not on RR. Question 24: B C E Regarding Jocantaro's doubts if either C or D I think it should be C since as the vSmart learns the routes from the Branches, it advertises to other branches that those will have it's TLOC IP changed to the Hub's TLOC, making it a hub-and-spoke topology. From the email it says "Any such communication be instead routed through the data center where we have the necessary firewalls in place." a) Create an ACI at Branch #1 and Branch #2 blocking their direct mutual communication b) Create POS VPN AND VPN interface feature templates and apply them to Branch #1 and Branch #2 device templates c) Apply the policy outbound to the Site IDs of Branch #1 and Branch #2 d) Apply the policy outbound to the Site ID of the DC e) Create a policy to set the TLOCs for Branch #1 and Branch #2 POS OMP routers to the DC TLOC(s) f) Block Branch #1 and Branch #2 from learning each other’s TLOC routers Question 26: A C B - Definitely not as it's VPN512 D - There's no direct Internet on vEdge52 VPN0 which is going to SP#2 E - Definitely not as there's no direct Internet from vEdge51 to the TLOC extension to vEdge52. Based on the given constraints and existing design, which two steps can be performed to ensure that internet-bound traffic from Branch #2 is not sent via the data center?(Choose two.) a) On Vedge52, configure NAT to VPN 0 on the interface connected to the vedge51 TLOC extension interface for the internet transport. b) On vedge51, configure NAT to VPN 512 on the interfaces toward the ISP. c) On vedge51, configure NAT to VPN 0 on the interface toward the ISP. d) On vedge52, configure NAT to VPN 0 on the interface toward SP #2. e) On vedge51, configure NAT to VPN 0 on the TLOC extension interface for the internet transport. Question 27: C D C - Need to restrict the Guest VPN D - For DIA Which two steps are required to implement the desired Guest VPN design? (Choose two) a) Implement a localized data policy that blocks Guest VPN traffic between SD-WAN branches. b) Configure a centralized VPN membership policy that only allows Guest VPN prefix to be advertised in OMP. c) Configure a centralized VPN membership policy that restricts the Guest VPN prefix from being advertised in OMP. d) Configure centralized data policy that perform NAT of Guest VPN traffic to VPN 0. e) Configure a localized control policy that rewrites the TLOC of Guest VPN routes in OMP to 0.0.0.0.

Interested. Let me know