Refer to the exhibit. Users in AS 65010 are connected with the application server in AS 65050 with these requirements: - AS 65010 users are experiencing latency and congestion to connect with…

Applying an AS-Path route-map policy for traffic received from R3 is typically used to filter or modify routes locally based on their AS-Path, not to prevent AS 65030 from being transient or to directly influence AS 65010's outbound path.

Configuring a route-map on R3 (assuming R3 is in AS 65030) to prepend its AS-Path when advertising routes to R5 (in AS 65010) makes paths through AS 65030 appear longer. This discourages R5 from sending traffic via AS 65030, effectively restricting AS 65030 from becoming a transient autonomous system for this traffic.

Applying a MED route-map policy for traffic received from R4 would usually involve R5 modifying the MED on incoming routes, but MED is primarily used for influencing inbound traffic selection by other ASes, not the local AS's outbound path.

Configuring a higher Local Preference for R5-R4 BGP peering is a highly effective and common method for AS 65010 to prefer outbound paths via AS 65040; however, it is not selected as one of the two correct answers.

To efficiently utilize underutilized links to AS 65040, R5 (in AS 65010) needs to prefer routes from AS 65040 (R4). Configuring a route map to set a lower MED (e.g., 50) for routes received from R4 makes those paths more attractive to R5 compared to paths from other ASes (like AS 65030), assuming MED comparison is enabled or relevant.