Correct Answer: A. Present a focused subset of a large model for a particular audience
Explanation:
Perspectives simplify model navigation by exposing relevant tables, measures, and hierarchies.
They improve usability but are not a substitute for security.
Correct Answer: D. Which users can access specific models, dimensions, members, and measures
Explanation:
Analytical security restricts data and model objects according to user roles.
It must be enforced in the model rather than relying only on report filters.
Correct Answer: C. To combine fast multidimensional summaries with relational storage for detailed data
Explanation:
HOLAP balances MOLAP-style aggregate speed with ROLAP-style detailed scalability.
The architecture is useful when detail volume is too large for full MOLAP storage.
Correct Answer: B. Scalability and relational freshness depend on database query performance
Explanation:
ROLAP queries relational tables rather than storing all detail multidimensionally.
This supports large or frequently changing data but requires strong relational tuning.
Correct Answer: C. A coordinate formed by one member from one or more dimensions
Explanation:
A tuple identifies a cube cell or slice coordinate across dimensions.
For example, one Product member and one Time member can identify a specific context.
Correct Answer: A. To process, manage, and query separate data segments independently
Explanation:
Partitions isolate periods or other segments for incremental processing and maintenance.
Only the affected partition may need to be refreshed after a new load.
Correct Answer: D. When dimension members or attributes changed and existing data should be retained where possible
Explanation:
Process Update incorporates dimension changes without always performing a complete rebuild.
Depending on relationships, affected aggregations or indexes may still require reprocessing.
Correct Answer: B. Precompute useful summaries that improve query speed without excessive processing and storage
Explanation:
Aggregations trade storage and processing time for faster retrieval.
A good design targets common queries and hierarchy paths rather than materializing everything.