All MCQs

Logical design expresses how analytical data is organized for business use.
Physical storage and indexing decisions are addressed later.

A conceptual model communicates major business entities and scope.
It avoids implementation detail and supports shared understanding with stakeholders.

Profiling reveals what source data actually contains rather than what documentation claims.
Its findings shape mappings, cleansing rules, and feasibility decisions.

Requirements define what decisions and processes the warehouse must support.
They provide the basis for modeling, sourcing, testing, and delivery.

The executive is exploring measures across multiple analytical dimensions.
That multidimensional historical analysis is the defining use of OLAP.

Posting deposits and withdrawals is routine transaction processing.
The other choices analyze historical data rather than record operational events.

Committed operational transactions represent legally and financially important events.
Warehouse aggregates can often be rebuilt, but lost transactions may not be recoverable.

OLAP is built for analysts, managers, and decision-makers.
Operational users interact with applications that execute routine transactions.

Warehouses accumulate records across systems and over long time periods.
Operational systems may retain less history or archive it elsewhere.

Customer-facing transactions require rapid, predictable completion.
Complex analysis may tolerate slightly longer responses because it processes more data.

OLAP questions often require multiple joins, filters, groups, and calculations.
OLTP statements are usually narrow and designed for a specific transaction.

Isolation controls how concurrent transactions see each other’s changes.
It is central to reliable operational processing, especially under heavy concurrency.