Workday-Adaptive-Planning Exam Questions

In Workday Adaptive Planning, Dimensions and Attributes serve fundamentally different purposes within the planning model. Dimensions are used to tag and categorize planning data during entry or import --- they are applied to sheets and accounts to enable multi-dimensional data input and reporting along axes such as Product, Project, Customer, or Location. When a dimension is added to a sheet, planners can enter data at the intersection of the dimension value, level, account, and time period. Attributes, by contrast, are used to tag existing model elements such as levels or accounts with descriptive metadata. For example, a Level Attribute might classify each level as a 'Cost Center Type' (Shared Services, Direct, etc.), or an Account Attribute might tag accounts by 'P&L Category.' Attributes do not create new data input axes --- they add descriptive properties to existing elements for filtering and grouping in reports. This distinction is fundamental to Adaptive Planning's dimensional architecture. Reference: Workday Adaptive Planning --- Dimensions vs Attributes, Dimensional Architecture, Model Design.

When expense results in a linked OPEX model appear under the 'Uncategorized' location dimension value, it indicates that the source personnel sheet data does not carry location dimension information. In Workday Adaptive Planning, when a cube or modeled sheet references data from another sheet via a linked account formula, the dimension values present in the results are determined by the dimension values present in the source data. If the personnel sheet was not planned with the location dimension --- meaning location was not used as a planning axis when entering headcount data --- then the location dimension has no value assigned to those rows, and the system classifies them as 'Uncategorized' in the OPEX output. The solution is to configure the personnel sheet to include the location dimension as a planning axis, so that headcount entries are tagged with specific location values. Adding formula term modifiers for location in OPEX would not resolve the root cause, which is missing dimensional data at the source. Reference: Workday Adaptive Planning --- Dimensional Data Linking, Location Dimension, Cube Sheet Architecture.

In Workday Adaptive Planning modeled sheets, a value lookup for dimensions or text selector columns serves the primary function of associating specific values to dimension or text fields over time, which are then referenced in formula calculations within the modeled sheet. For example, a value lookup might associate a specific benefit election (e.g., 'Family Plan') with a corresponding rate value that changes over time periods --- enabling the modeled sheet formula to look up the appropriate rate based on the selected dimension value and time period. This lookup mechanism is what powers time-sensitive, dimension-driven calculations in complex planning models such as HR, benefits, compensation, and sales planning. It is not used for entering global assumption values (which is done directly in Assumption accounts), nor for general data entry into model columns, nor for time-spreading functions (which is handled by Splits/Breakback). The value lookup is a purpose-built mechanism for dynamic, time-aware dimensional rate association. Reference: Workday Adaptive Planning --- Modeled Sheets, Value Lookups, Dimension Calculations.

When importing new levels into Workday Adaptive Planning via the level import process, the 'Rolls up to' field is a required data element. This field specifies the parent level to which the new level reports, defining its position within the organizational hierarchy. Without the 'Rolls up to' value, the system cannot place the level correctly in the hierarchy, making it an essential import requirement. The import file for levels typically requires: the level name, the level code, and the 'Rolls up to' parent reference. While the level Code is also important for identification, among the options listed, 'Rolls up to' is the critical structural requirement that determines hierarchy placement. Short name is optional metadata. Currency can default to the corporate currency if not specified for individual levels. The 'Rolls up to' field is the hierarchical anchor that the system mandates to establish parent-child relationships during bulk level imports. Reference: Workday Adaptive Planning --- Level Import, Required Level Fields, Hierarchy Configuration.

In Workday Adaptive Planning, General Ledger accounts are created under Root accounts, which are the primary account categories forming the top level of the Chart of Accounts hierarchy. Root accounts represent the major financial statement categories --- such as Assets, Liabilities, Equity, Revenue, and Expenses --- and serve as the parent containers under which all user-created GL accounts are organized. Prepaid Advertising is an asset or operating expense account in standard accounting classifications, and the new GL account would be created as a child of the appropriate Root account category (e.g., under Assets for a prepaid classification, or under Operating Expenses). The navigation path is Modeling > Model Management > Accounts, where the administrator selects the relevant Root account and creates the new GL account beneath it. System accounts are pre-configured accounts managed internally by Adaptive Planning for system-level processing and cannot be created by users. Assumption accounts are reserved for global planning constants such as rates and percentages, not transactional GL accounts. Contra accounts are a sub-classification used to offset specific account balances (e.g., Accumulated Depreciation offsetting Fixed Assets) and are not a primary creation category for new accounts. Reference: Workday Adaptive Planning --- Chart of Accounts, Root Accounts, GL Account Creation, Model Management.