When an ACL is applied inbound on the Internet gateway interface facing the internal (trusted) network, the source IP address seen in the ACL will be the address after NAT translation has been applied to outbound traffic. This is called the inside global address:
* Inside global = Public IP assigned by NAT to inside traffic for external use.
* Inside local = Internal IP address prior to NAT.
Why other options are incorrect:
* B, D: Outside addresses refer to external devices, not internal traffic.
* C: Inside local is seen before NAT, not after.
-

# Explanation:
* A: Traditional project management (often referred to as the Waterfall model) involves a fixed sequence of phases-planning, design, execution, and delivery. Client involvement is typically high at the beginning (requirements gathering) and low during implementation.
Other options:
* B, C, and D (LEAN, Kanban, Agile): These emphasize continuous feedback, flexibility, and frequent customer interaction throughout the project lifecycle. Agile in particular encourages constant client collaboration via sprints and reviews.

In a full-mesh iBGP design, every router must establish and maintain a BGP session with every other router.
As the number of routers increases, the number of BGP sessions and the amount of BGP processing increases exponentially. This leads to high CPU utilization, especially in devices with limited processing capabilities, such as distribution routers.
Themost cost-effectiveandscalablesolution in this scenario is toimplement route reflectors (RRs)on the two core routers. Route reflectors significantly reduce the number of iBGP peerings required, eliminating the full mesh requirement by allowing the distribution routers (RR clients) to establish a single iBGP session with the route reflector. The route reflector handles route advertisement to other RR clients, thereby reducing overhead on the distribution routers.
This solution adheres to CCDE v3.1 design principles for:
* Optimizing control plane scalability
* Reducing unnecessary CPU load from control protocols
* Ensuring a maintainable and scalable enterprise BGP deployment
Why the other options are incorrect:
* BandD(Increasing memory): Addresses only hardware capacity without solving the root cause (BGP scaling issue).
* C(Using eBGP): Misaligned with enterprise internal network design; eBGP adds complexity in route policy and administrative boundaries.
* E(Increasing bandwidth): Bandwidth does not alleviate CPU overhead caused by BGP processing.
Implementing route reflectors aligns with both scalability and cost-efficiency goals as prescribed in the CCDE v3.1 methodology.

* C (PIM Sparse Mode with RP located at the hub):DMVPN networks typically leverage sparse mode multicast due to their efficiency in dynamic topologies. Locating the Rendezvous Point (RP) at the hub simplifies multicast state management, since the hub serves as the central aggregation point and ensures optimal rendezvous functionality without requiring complex RP placement across spokes.
Other options explained:
* A: Dense mode is inefficient and generates unnecessary flooding, especially in WAN environments.
* B/D: Placing RPs at remote sites introduces unnecessary complexity and operational challenges.

When logical VRF separation is based on fields like IP address ranges or packet characteristics (such as packet length), the most scalable solution is:
* Policy-Based Routing (PBR): This allows traffic to be classified and forwarded into the correct VRF based on flexible match conditions like source IP address, destination IP address, or packet size.
Why other options are incorrect:
* A: Static route leaking lacks flexibility and scalability for dynamic classification.
* C: OSPF per VRF handles control-plane separation, but not data-plane traffic classification.
* D: MP-BGP is used for control-plane VPN route exchange, but not for VRF selection based on traffic attributes.
-