Question 12

Explanation

Option D is CORRECT. The LookML modeling layer in Looker defines business metrics, calculations, relationships, and rules in a centralized, version-controlled codebase. This ensures that metrics like "revenue" or "conversion rate" are calculated consistently across all reports and dashboards, regardless of who creates them. The LookML model serves as a single source of truth for metric definitions, eliminating discrepancies that occur when calculations are defined ad-hoc in individual reports.

Option A is INCORRECT. Custom fields in Looker (or Looker Studio) are created within individual reports or dashboards, not centrally defined. This approach actually contributes to inconsistency as different report creators might define similar metrics differently, leading to contradictory results across the organization.

Option B is INCORRECT. Data blending combines data from multiple sources but doesn't ensure consistent metric definitions. It's a technique for joining datasets rather than standardizing business logic across reports.

Option C is INCORRECT. Calculated fields, like custom fields, are typically defined within individual reports or explorations. While useful for ad-hoc analysis, they don't provide the centralized definition repository that ensures consistency across all reports and dashboards in the organization.