A report can wait, and interactive users need priority. What do you use for the report?
Why A is the answer
A batch query job
A report that can wait should run as a batch job, so that interactive users keep priority.
In detail
- Batch query jobs wait for capacity, so interactive users come first.
- Batch queries wait for idle capacity.
Use case
An illustrative scenario, not a real incident.
A monthly report runs as a batch query, which leaves interactive users unaffected.
See it in different ways
stateDiagram-v2 [*] --> QueryPlan QueryPlan --> PartitionAndCluster: scans too much QueryPlan --> MaterializedView: repeated aggregation QueryPlan --> BiEngine: dashboards need sub-second PartitionAndCluster --> [*] MaterializedView --> [*] BiEngine --> [*]
flowchart TD
Q{"Is someone waiting?"}
Q -->|"Yes"| A0["Interactive"]
Q -->|"No"| A1["Batch"]Key point: Batch jobs can wait.
Why the other options are wrong
- B. An interactive query
- An interactive query competes with users.
- C. A BI Engine reservation only
- BI Engine is for dashboards.
- D. A failover replica
- A replica is for availability.