Workday-Adaptive-Planning Exam Questions

In Workday Adaptive Planning, a single value lookup table for the Benefit Election dimension is the correct design to drive different calculation rates based on which benefit election a user selects in a modeled sheet. A value lookup table maps each dimension value (e.g., Single, Family, Employee+Spouse) to a corresponding rate value, enabling the modeled sheet formula to dynamically look up the appropriate rate for whichever benefit election is selected on each row. This architecture is efficient, maintainable, and requires only one lookup object rather than separate tables per dimension value. Creating a separate value lookup table for each dimension value (Option C) is unnecessarily complex and duplicates data structures. A cube sheet (Option B) could store rate assumptions but requires a more complex reference architecture than a simple value lookup. A Rate dimension attribute (Option D) stores static metadata on dimension values and cannot drive time-sensitive rate lookups in calculations. The single value lookup table per dimension is the official, recommended pattern in Adaptive Planning's modeled sheet design. Reference: Workday Adaptive Planning --- Value Lookup Tables, Modeled Sheets, Dimension-Driven Calculations.

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 formula syntax, [time=this.year-1] is the correct and officially supported modifier to retrieve the full prior fiscal year value of an account. This modifier navigates to the year period that is one year before the current year context, returning the annual total for the previous fiscal year --- which is the precise requirement for incorporating full-year prior year expenses into a formula. Option A uses [time=last.year], which is not standard Adaptive Planning formula syntax and would result in a formula error. Option C uses [year=previous], which is also not valid Adaptive Planning formula notation. Option D uses [time=this-12], which shifts back 12 months --- for a monthly formula, this returns the same month from the prior year, not the full prior year total. When a formula needs the full prior year annual amount (sum of all 12 prior months), [time=this.year-1] retrieves the aggregated annual value. This is the authoritative time modifier syntax for annual prior year references in Adaptive Planning. Reference: Workday Adaptive Planning --- Time Modifiers, Prior Year Reference, Formula Syntax Guide.

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.

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.