A LookML developer creates a new model and a test dashboard from the model. The developer shares the link to the new dashboard with users, but the users report that all they see is the "Model Not Found" error.
What is a possible cause of this issue?

A developer is building an e-commerce Explore with the following datasets: orders and users. The business user needs to be able to answer questions about sellers and buyers within the same Explore. Each order in the orders table reports a buyer and seller ID. The users table has the detailed information about the individual buyer and seller.
How should the Explore be defined to meet this requirement?
A)

B)

C)

D)

A LookML developer has written the following persistent derived table. It references orders_rollup, another persistent derived table that also rebuilds with the same SQL trigger value.

Which change is needed to guarantee that user_facts will always rebuild with the latest data from orders_rollup?

A user reports that a query run against the orders Explore takes a long time to run. The query includes only fields from the users view. Data for both views is updated in real time. The developer runs the following query in SQL Runner and quickly receives results:
SELECT * FROM users.
What should the developer do to improve the performance of the query in the Explore?

A developer wants to create a measure that shows the item count broken out by category. When a second, more granular dimension is added to the same query, the count broken out by category should still represent the original aggregation and be duplicated on each line. The business wants this "count" in "category" available in the Explore section without any additional work done by the end user. For example:
The Count column represents the count for each combination of Category and Item.
The Count in Category column represents the count for each Category only.

How can the developer address this need with a LookML object?