Question 290
An implementation decision is needed: A database query should keep a stable key, quantity and price, but dozens of unused binary and comment columns inflate refresh. What should the analyst do?
Explanation
Correct Answer
This directly addresses the stated constraint. Column projection should remove unused attributes without losing required relational keys. Confirmation: The resulting model exposes only required columns and refresh payload is reduced.
Incorrect Answers
A page-level filter hides future records but leaves the underlying timestamp conversion wrong. The specific problem here is that removing the business transaction key breaks later relationships and reconciliation.
Removing duplicates by invoice date alone deletes legitimate sales occurring on the same day. The specific problem here is that removing the business transaction key breaks later relationships and reconciliation.
Changing only the display format leaves mismatched underlying text/integer key types. The specific problem here is that removing the business transaction key breaks later relationships and reconciliation.