After running the LookML Validator, a developer sees the following error message in the Looker development environment:
"Measures with Looker aggregations (sum, average, min, max, list types) may not reference other measures".
What could be causing this error?

A user reports the following SQL error when selecting the discounted sale price field:
ERROR: column "order_items.sale_price"; must appear in the GROUP BY clause or be used in an aggregate function.
The developer checks the field definition and finds it to be:
measure: discounted_sale_price {
type: number
sql: ${sale_price} * 0.8 ;;
}
The developer also finds the LookML definition of the sale_price field to be:
dimension: sale_price {
type: number
sql: ${TABLE}.sale_price ;;
}
What is the likely cause of the SQL error?

A developer wants to calculate the ratio of total sales from the orders view and total users from the users view.
Which two methods can be used to create a measure that meets these requirements? (Choose two.)

B)

C)

D)

E)

A developer needs to build a new dimension that offers an age-based cohort representation of users.
Which LookML code should the developer use to meet the requirement?
A)

B)

C)

D)

A developer is connecting a LookML project to a remote Git repository. The developer wants to track which users are committing code changes, creating pull requests, or deploying to production when the different Git commands are initiated from within Looker.
Which type of Git connection should be utilized to meet this business requirement?