Does an NDT with bind_all_filters: yes need to be joined into the same Explore specified in its explore_source parameter?

When using a non-driving table (NDT) that has the parameter bind_all_filters: yes, it is essential for it to be joined into the same Explore specified in its explore_source parameter. This is because bind_all_filters: yes means that all filters defined on the NDT will impact the results of the Explore, and for these filters to effectively apply and provide meaningful data, the NDT must be part of the Explore where the filters are applied.

By joining the NDT into the specified Explore, you ensure that the filters are automatically bound to it, allowing for the intended behavior where the data returned is filtered according to the criteria set by the filters in the Explore. If the NDT were to be used outside of the specified Explore, the filters would not have the desired effect, leading to potential discrepancies in the results produced and making the data less reliable.

While other options suggest varying degrees of scenarios regarding the NDT and its filter settings or propose conditions under which this might not hold true, they do not account for the fundamental functionality provided by bind_all_filters: yes. Thus, the distinct requirement that the NDT needs to be joined into the same Explore for the filters to work correctly affirms the correctness