Company ABC is in process of configuring BGP confederation between its sites.
For the moment, BGP has been configured between R1 - R3 and R1 - R2, while in the following weeks, there will be no BGP peering between R3 and R2.
The direct link between R3 and R2 was recently installed and a static route was configured on R3 for site-2 network, 192.168.200.0/24, to use the new link.

quiz-16-1

Until the moment that BGP will be configured between R3 and R2, you do not want to advertise site-2 (R2) network, 192.168.200.0/24 towards your external partner, AS 400.


Here is the current status: 
============= on R3 ===================
R3#sh ip bgp
...
   Network          Next Hop            Metric LocPrf Weight Path
*> 10.0.0.0         10.0.0.4                 0             0 400 i
*> 192.168.100.0    192.168.13.1             0    100      0 (65100) i
r> 192.168.200.0    192.168.12.2             0    100      0 (65100 65200) i

============= on R4 ===================
R4#sh ip bgp
...
   Network          Next Hop            Metric LocPrf Weight Path
*> 10.0.0.0         0.0.0.0                  0         32768 i
*> 192.168.100.0    10.0.0.3                               0 123 i
*> 192.168.200.0    10.0.0.3                               0 123 i

How can you achieve the task (don't advertise 192.168.200.0/24 to R4) without modifying the ALLOW-ALL route-map (or applying other policies to the BGP neighbors) ?
The configuration needs to be applied only on R3.

Post your answer in the ‘Comments’ section below and subscribe to this blog to get the detailed solution and more interesting quizzes.