A developer commits changes after adding LookML for a new measure. Upon pulling from production, the developer notices the following lines in the LookML:

The developer has moved the orders Explore (shown below) from model_a to model_b, where both models are in the same project, and all users have access to both models.
Connection: "demo"
include: ".view"
explore: orders {}
What will happen after making this change?

Users report that every time they change the filter on their Explore, the filters take a very long time to populate.
How can the developer improve the filtering experience with this Explore?

Users viewing an Explore should be able to view rows of data only where the value of the product.brand column matches the value of the user's company user attribute.
Which access filter should the developer use to meet this requirement?
A)

B)

C)

D)

A developer needs to add an Explore built off of the orders view, which surfaces only completed orders. An orders Explore exists that contains all order information. Fields from the orders view are also referenced in other existing views such as ${orders.fieldname}.
How should developer define a new Explore for completed orders and keep all field references working correctly?
A)

B)

C)

D)