150-230 · Question #201
Referring to the exhibit, which network will be advertised to AS 701?
The correct answer is B. 198.92.150.0/23. See the full explanation below for the reasoning.
Question
Referring to the exhibit, which network will be advertised to AS 701?
Options
- A63.83.207.0/24
- B198.92.150.0/23
- C63.83.225.0/24
- D65.247.178.0/23
How the community answered
(55 responses)- A15% (8)
- B75% (41)
- C4% (2)
- D7% (4)
Community Discussion
7
Mateus R.May 7, 2026Think of BGP route aggregation like a hotel front desk that only tells guests "the restaurant is on the second floor" rather than listing every individual table. When a router is configured to summarize, it advertises the big summary block outward and keeps the specifics to itself. The correct answer is B, 198.92.150.0/23. In the exhibit, the local AS has an aggregate-address statement or a network statement covering 198.92.150.0/23, and that is the route being injected into BGP for advertisement to the neighboring AS 701. The more specific /24 routes in the 63.83 and 65.247 address space either belong to that same AS or are being suppressed by the aggregation, so they do not get sent across the eBGP session. The /23 is the one coherent summary that the router is configured to originate and share, and that is exactly what AS 701 receives in its BGP table.
Samuel O.May 4, 2026The trick here is recognizing that BGP will advertise the aggregate summary out to that neighbor rather than the more specifics, which is exactly what you'd configure to keep your routing table lean when peering with an upstream provider. Have you worked out yet whether the other three options would be suppressed entirely or just not originated into the update, and does that distinction change how you'd troubleshoot a missing prefix on the far end?
Mateus R.May 4, 2026Right on the aggregate behavior, though the suppressed-versus-not-originated split is worth nailing down for the exam because a suppressed component still sits in the BGP table with an "s" flag, like a box in a warehouse that got held back from the delivery truck, so "show bgp ipv4 unicast" will reveal it, whereas a prefix that was never originated is simply absent, and that difference tells you immediately whether your troubleshooting should target the summarization config or a missing network statement upstream.
Ingrid P.May 13, 2026B, the /23 gets the summary route advertised. Saw this exact aggregate-address scenario on my real exam, almost picked A until I remembered the suppress-map card I had drilled the night before.
Anjali D.May 23, 2026Saw this exact setup on my exam, the summary route B was the only one that fit the aggregate.
Ingrid P.May 24, 2026That tracks for aggregate behavior, but make sure you have a card for why the other routes fail the aggregate condition specifically, not just that route B wins, because the exam will probe that distinction from multiple angles.
Ola B.May 2, 2026Spin up the lab, does aggregate-address push the /23 summary out?