Complete Solutions With Clear Explanations
2026/2027.
Domain 1: The DISCO Framework, the Lists & the Data Hub Architecture (14 Questions)
1. A planning model requires a module to stage raw transactional data imported from an ERP
system before any transformations are applied. According to the DISCO framework, which
module type is strictly designated for this purpose?
A) Input
B) System
C) Calculation
D) Data
[CORRECT] D
Rationale: The DISCO framework dictates that the Data module is specifically designated as
the source staging area for raw transactional data imported from external systems before any
business logic or transformations are applied.
2. An Anaplan architect is designing a model and needs to create a module where regional
managers enter their quarterly headcount assumptions. Which DISCO module type should
house this assumption entry?
A) Input
B) Output
C) System
D) Data
[CORRECT] A
Rationale: The Input module is specifically designated for user-entered assumptions and
planning inputs, such as headcount assumptions, isolating them from system logic and
calculations.
,3. Complex revenue allocation formulas and advanced business logic have been built directly
in the Output module, causing dashboard load failures. According to DISCO principles, where
should this logic reside?
A) Calculation
B) System
C) Data
D) Output
[CORRECT] B
Rationale: The DISCO framework dictates that complex business logic, such as revenue
allocation formulas, must be stored in the System module. The Output module should only be
a dimensional slice for the dashboard, fed by the System module.
4. A stakeholder requests a reporting view that slices the aggregated revenue by region and
product for a dashboard. Which DISCO module type fulfills this requirement?
A) Data
B) Input
C) Calculation
D) Output
[CORRECT] D
Rationale: The Output module is specifically designed as a dimensional slice for reporting UX
and dashboards, aggregating results from Calculation and System modules without housing
its own complex logic.
5. An architect needs to import detailed general ledger transactions, but the records lack a
unique natural key and may contain duplicate names. Which list structure should be used to
load this transactional source data?
A) Composite List
B) Numbered List
, C) Hierarchical List
D) Subset
[CORRECT] B
Rationale: A Numbered List is specifically used to create a flat, non-hierarchical structure for
transactional source data where items lack unique names, allowing duplicates by generating a
unique system-generated ID behind the scenes.
6. Why is a Numbered List the optimal design choice for loading high-volume sales receipt
records into an Anaplan model?
A) It enables the automatic aggregation of data to parent hierarchies.
B) It ensures a flat, non-hierarchical structure where duplicate item names are uniquely
identified by a system-generated ID.
C) It allows for direct input on the list properties.
D) It reduces the overall cell count by compressing data.
[CORRECT] B
Rationale: A Numbered List provides a flat, non-hierarchical structure specifically for
transactional source data, ensuring duplicate names (like "Invoice 123" from different
sources) can be loaded and uniquely identified via a system-generated ID.
7. When configuring a Numbered List for transactional data imports, what is a mandatory
architectural requirement to ensure users can identify the records?
A) A parent hierarchy must be defined.
B) Selective Access must be enabled on the list.
C) A display name property line item must be created in a System module.
D) The list must only contain one line item.
[CORRECT] C
Rationale: Because a Numbered List uses system-generated IDs, a display name property line
item must be created in a corresponding System module so users can identify the actual
transaction names instead of viewing arbitrary ID numbers.