A Data Engineer is building a set of reporting tables to analyze consumer requests by region for each of the Data Exchange offerings annually, as well as click-through rates for each listing. Which vi

Question

Options

• ASNOWFLAKE.DATA_SHARING_USAGE.LISTING_EVENTS_DAILY
• BSNOWFLAKE.DATA_SHARING_USAGE.LISTING_CONSUMPTION_DAILY
• CSNOWFLAKE.DATA_SHARING_USAGE.LISTING_TELEMETRY_DAILY
• DSNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY

• A
  6% (3)
• B
  86% (42)
• D
  8% (4)

Explanation

LISTING_CONSUMPTION_DAILY (B) captures consumer request activity per listing - including regional breakdowns and date granularity needed for annual aggregation - making it the right source for the "requests by region" requirement. LISTING_TELEMETRY_DAILY (C) records impression and click-through metrics per listing, directly satisfying the click-through rate requirement. Together, B and C provide the minimal set that covers both analytical needs.

Why A is wrong: LISTING_EVENTS_DAILY tracks discrete listing events (e.g., listing get/request actions) but lacks the regional consumption detail and telemetry metrics needed here; B and C already cover its relevant scope more completely.

Why D is wrong: DATA_TRANSFER_HISTORY (under ACCOUNT_USAGE, not DATA_SHARING_USAGE) tracks inter-account data egress volumes and costs - it has nothing to do with Data Exchange listing analytics or consumer behavior.

Memory tip: Split the two requirements and match them to the view name: Consumption = Consumers requesting data by region; Telemetry = Tracking clicks (CTR). If the view isn't under DATA_SHARING_USAGE, it's almost certainly a distractor for Data Exchange questions.

No community discussion yet for this question.