To use an IPv6 link-local address as a next hop, which type of static route must be configured?

Using an IPv6 link-local address as a next hop requires a fully specified static route. This is because a fully specified route provides both the destination IP address and the next-hop address, along with an interface. With IPv6 link-local addresses, which are only accessible on the local link and are not routable beyond that link, the interface must be specified to inform the router which local network segment to use for the communication.

In a fully specified static route, the syntax typically includes the next-hop address along with the interface identifier. For example, you might see a command where both the link-local address and the associated interface are explicitly defined, ensuring the router can correctly identify the right path on the local network.

Other options are less appropriate in this context. Directly attached static routes may typically refer to destinations directly connected to the router without the need for specifying interfaces. Recursive routes rely on the routing table to resolve the next-hop address, which isn't applicable with link-local addresses because they can't be resolved in this manner. General static routes don’t guarantee the inclusion of interface information, which is essential for link-local addresses. Thus, a fully specified static route is the most suitable choice for using an IPv6 link-local address as the next hop.