Redundant Trunk Groups (RTGs) on EX Series switches provide a simple solution for network recovery when a trunk port on a switch goes down 1 .  They are configured on the access switch and contain two links: a primary or active link, and a secondary link 1 .  Therefore, option B is correct because if the active link fails, the secondary link automatically starts forwarding data traffic without waiting for normal spanning-tree protocol convergence 1 .

Option D is also correct.  In a typical enterprise network composed of distribution and access layers, RTGs are used where one Access switch is connected to two different uplink switches 2 .  This implies that RTGs must be connected to the same aggregation switch 2 .

Aggregate routes are used for advertising summarized network prefixes 1 2 .  They help minimize the number of routing tables in an IP network by consolidating selected multiple routes into a single route advertisement 1 .  This approach is in contrast to non-aggregation routing, in which every routing table contains a unique entry for each route 1 .

Therefore, option D is correct. Options A, B, and C are not correct because:

Aggregate routes can be used with both static routing and dynamic routing protocols 1 .

Aggregate routes are not automatically generated for all of the subnets in a routing table.  They need to be manually configured 1 .

Aggregate routes are not always preferred over more specific routes.  The route selection process in Junos OS considers several factors, including route preference and metric, before determining the active route 1 .

BGP is a routing protocol that operates between autonomous systems (AS). An AS is a group of routers under a single administrative control. BGP can be classified into two types: internal BGP (IBGP) and external BGP (EBGP). IBGP is the BGP communication between routers within the same AS, while EBGP is the BGP communication between routers in different AS. BGP uses the AS_PATH attribute to record the AS numbers that the route has passed through, and uses it to prevent routing loops and select the best path.

In this scenario, you want to add a second ISP connection and remove the default route to the existing ISP. This means that you want to have more control over the routing decisions and use BGP to exchange routes with both ISPs. To do this, you need to deploy the BGP protocol in your network and configure both IBGP and EBGP sessions. The correct statements about BGP in this scenario are:

IBGP peers advertise routes received from EBGP peers to other IBGP peers. This is the default behavior of IBGP, as it allows the routers within the same AS to learn the routes from different EBGP peers and select the best exit point. However, IBGP has a rule that it does not advertise routes received from IBGP peers to other IBGP peers, to avoid creating routing loops. Therefore, option B is correct and option C is incorrect. To overcome this rule, IBGP requires a full mesh topology, where every IBGP router is directly connected to every other IBGP router, or a route reflector or confederation design, where some IBGP routers act as intermediaries to reflect or aggregate the routes to other IBGP routers.

EBGP peers advertise routes received from IBGP peers to other EBGP peers. This is the default behavior of EBGP, as it allows the routers in different AS to exchange routes and reachability information. However, EBGP has a rule that it does not advertise routes received from EBGP peers to other EBGP peers, to avoid creating routing loops. Therefore, option D is correct and option A is incorrect. To overcome this rule, EBGP uses the AS_PATH attribute to filter out the routes that contain its own AS number, or uses route maps or policies to control the route advertisement. IBGP does not update the next-hop attribute to ensure reachability within an AS, as the next-hop attribute is preserved by IBGP. Instead, IBGP relies on an underlying IGP (Interior Gateway Protocol) to provide reachability to the next-hop.