A regional sales team works offline on long-haul flights and queries a 40-million-row table on a corporate database that throttles ad-hoc analytical reads during business hours. The team needs fast filtering and aggregation in the workbook without hitting the source repeatedly. Which connection approach best fits these constraints?
- ACreate an extract so the data is stored locally for offline use and fast in-memory querying that avoids repeated load on the throttled source. Correct
- BKeep a live connection so every interaction reflects the current state of the corporate database in real time.
- CUse a live connection but lower the workbook's refresh frequency so the database receives fewer queries during business hours.
- DKeep a live connection and rely on the source database's own result cache to satisfy offline interactions.
Why A is correct: An extract snapshots the data into a local columnar store, which works offline and serves fast filtering and aggregation from memory without querying the throttled source each time.
Why B is wrong: A live connection sends a query to the source on every interaction, which fails the offline requirement and worsens the throttling problem the team is trying to avoid.
Why C is wrong: There is no per-interaction refresh frequency to lower on a live connection; each view interaction still issues a query, so this does not solve offline access or throttling.
Why D is wrong: A source-side cache cannot serve a disconnected client; with no network the live connection has nothing to query, so offline analysis is impossible.