You are creating a static route with a next hop that is not directly connected.

In Junos, a static route normally expects its next hop to be directly reachable on a connected interface. When the configured next hop is not directly connected, the router must determine how to reach that next hop using an existing route in the routing table. The resolve feature provides this behavior by allowing Junos to recursively resolve the configured static next hop through another route, such as an IGP learned route, a directly connected route to an intermediate device, or even another static route. Once the system can resolve the next hop to a usable outgoing interface and a final forwarding next hop, the static route becomes active and can be installed in the forwarding table.

This is common in data center environments where you want to point a static route at a loopback address, a service node address, or a next hop that is reachable through the fabric underlay rather than a directly connected subnet. With resolve enabled, the static route’s validity follows the reachability of the recursive path. If the supporting route used for resolution disappears, the static route is withdrawn, helping avoid blackholing traffic toward an unreachable next hop.

The qualified next hop feature is used to define primary and backup next hops with different preferences for the same static route, not to solve indirect reachability by itself. The install and retain options influence route installation and retention behaviors but do not provide recursive resolution of a non-direct next hop.