Refer to the exhibit. A network engineer must meet these requirements to provide a connects, solution: - The customer connected to Area 2 needs to access the application in Area 1 on the…

R2 is an internal router within Area 1; setting a tag there would not be effective for controlling route leaking from Level 2 to Level 1 Area 2, which occurs at the L1/L2 border router R3.

R3 acts as the Level 1/Level 2 router connecting Area 1 (Level 1) and the core (Level 2). Setting a tag of 200 on R3 for the summary address 10.0.0.0/16 (which includes 10.10.10.0/24) provides a mechanism to selectively identify and control specific routes.

After tagging the desired summary route on R3, applying a route map to leak only Level 2 routes that match tag 200 into Level 1 Area 2 on R3 achieves the stated requirements. This ensures the 10.10.10.0/24 subnet is accessible, 20.10.30.0/24 is excluded (as it won't be tagged), and Area 2's routing table is condensed to only essential summary routes.

R4 is an internal Level 1 router within Area 2, not a Level 1/Level 2 border router, and therefore is not responsible for leaking routes from Level 2 to Level 1 Area 2.

R1 is an internal router within Area 1; setting a tag on R1 would not influence the process of leaking Level 2 routes into Level 1 Area 2 from the L1/L2 border router R3.