A user complains that the table they're using within a data module has too much historical data in it. The user would like to keep the old data available, but when using the table for any new…

Question

Options

• ACreate a navigation path for the newer entries.
• CCreate a calculated 'Order Date'.
• DCreate a copy of the table, and apply a filter to the 'Order Date' attribute.

• A
  82% (18)
• C
  5% (1)
• D
  14% (3)

Explanation

Option A is correct because, in a data module (e.g., IBM Cognos Analytics), a navigation path lets the developer define a filtered perspective on a table - restricting the view to newer entries based on Order Date - without duplicating or altering the underlying data. This satisfies both requirements: historical data remains intact and accessible, while reports using the navigation path see only the relevant newer records.

Option C is wrong because a calculated column derives or transforms a value (e.g., computing a date difference); it doesn't filter which rows are visible to a report, so it doesn't address the problem at all.

Option D is wrong because copying the table creates data redundancy and maintenance overhead. The point of keeping data in the original table is to avoid duplication - a filtered copy defeats that purpose and can lead to sync issues over time.

Memory tip: Think of a navigation path as a "window" into the table - it changes what you see without touching what's stored. Whenever an exam asks how to show a subset of existing data without copying or modifying it, think navigation path.

No community discussion yet for this question.