In this flow, data moves from ingestion to orchestration to propagation. CloudWorks is the component that loads data into the Data Hub, serving as the ingestion step. Once the data resides in the Data Hub, Data Orchestrator takes over to coordinate the next actions: run validation actions to ensure quality, perform transformation processes to prepare the data, and then execute model-to-model pushes to move the data to other models. This sequence—load, validate/transform, then push—reflects a logical data lifecycle: bring data in, ensure it’s clean and properly shaped, and finally distribute it to downstream models. The other options misplace steps (for example, having the hub trigger validations without the initial load, or having orchestration load data, or reversing the push triggering CloudWorks), which breaks the intended order of operations.

Subsidiary views are a tailored way to present a module’s data for end users, especially on dashboards. By saving a specific arrangement of dimensions, filters, and visible data, you create a clean, analysis-ready grid that readers can interact with to explore the numbers without changing the underlying model. This makes it easy to show exactly the metrics and perspectives needed for analysis or filtering, providing consistency across the dashboard and a focused user experience. They don’t speed up calculations—how fast calculations run depends on the formulas and data volumes, not on how the data is viewed. They also don’t hold constants; constants are defined in the model as separate items, not in views. And while you can export data from a subsidiary view, its primary purpose isn’t “all exports,” but delivering a preconfigured, user-friendly view for dashboards and analysis.

Roles determine who can access an entire module and what they can do within it. In Anaplan, a user is assigned to a role, and that role specifies the level of permission (such as view or edit) for each module in the model. Because modules are the organizational units that contain the data and calculations, the security boundary is set at the module level. Lists and cells are parts of the module structure or data, and access is governed by the module’s permissions rather than by granting access directly to those elements. Users themselves are the subjects who receive access through roles, not the target of access controls.

Storage per cell varies by data type, and the Boolean type is the most space-efficient. A Boolean stores a simple true/false value, which is fixed at one byte per cell in this context. That makes it the smallest, fixed storage cost among the common types. Numbers require more space to hold digits and precision, Text grows with length, and List/Date/Time Period involve additional structure to represent items or time-related data. So the one-byte-per-cell cost is characteristic of a Boolean, explaining why it’s the correct choice.

Page Builder is the user-facing tool in Anaplan used to create and arrange what end users see on a dashboard. It lets you build pages, group related content, and organize the layout using cards and boards. Cards display specific elements like grids, charts, KPIs, or lists, while boards help you arrange these cards into a coherent, interactive dashboard that presents high-level information clearly. This is different from tasks that store data, handle imports, or manage security roles, which are not what Page Builder is for. In practice, you’d use Page Builder to craft a sales or operations dashboard that users can interact with to monitor metrics and trends.