Which step in the configuration of filter-based forwarding controls the selection of tables that will share interface routes?

The configuration of filter-based forwarding involves the use of RIB groups to control which routing tables share routes for specific interfaces. By setting up a RIB group, you define a collection of routing instances that can be referenced together, allowing for shared routing information across those instances. This is particularly useful in scenarios where specific routing decisions need to be made based on various criteria, such as separating routing for different traffic types or services.

In this context, the RIB group acts as the backbone for route sharing between the defined routing instances. When you configure filter-based forwarding and designate RIB groups, you are effectively managing how traffic is forwarded based on the routing information stored in those tables, guiding the selection of routes from multiple instances.

The other steps, such as configuring the routing instance, setting up filter match terms, and defining member interfaces, play supportive roles within the overall configuration. While they are important for establishing how filtering and forwarding should occur, they do not directly govern how the routing tables will correlate and share routes among interfaces, which is the primary function of the RIB group configuration.