The accounting team needs to incorporate a new General Ledger account for Prepaid Advertising into the Adaptive Planning model. Under which primary account category can you create the new Prepaid Advertising account?
Correct Answer: A
In Workday Adaptive Planning, General Ledger accounts such as Prepaid Advertising are created under Root accounts, which are the primary account categories that form the top-level structure of the Chart of Accounts. Root accounts represent the highest level of the account hierarchy and include categories such as Assets, Liabilities, Equity, Revenue, and Expenses. Prepaid Advertising, being a prepaid asset or operating expense account in standard accounting, would be created as a child of the appropriate Root account category. System accounts are pre-built accounts managed by Adaptive Planning for system-level calculations and cannot be user-created. Assumption accounts are reserved for global planning constants like rates and percentages. Contra accounts are used to offset balances in specific accounts (e.g., Accumulated Depreciation) and are a sub-classification, not a primary creation category. The correct workflow is to navigate to Modeling > Model Management > Accounts and create the new GL account under the appropriate Root. Reference: Workday Adaptive Planning — Chart of Accounts, Root Account Structure, General Ledger Account Creation.
Within a modeled sheet where users can select from different Benefit Elections stored as dimension values, what can you create to drive different rates in formula calculations based on the Benefit Election dimension value selected?
Correct Answer: A
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.
An OPEX model uses headcount data linked from a personnel sheet. When testing with sample data, all expense results appear in the location dimension value of ‘Uncategorized.’ What corrections need to be made to populate the location values?
Correct Answer: A
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.
The financial analyst is updating the formula for the Office Supplies account and needs to incorporate the full year office supplies expenses from the previous fiscal year. What formula should the analyst implement to retrieve last year’s value?
Correct Answer: B
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.
What is a key difference in how Dimensions and Attributes are typically used?
Correct Answer: C
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.
Prep2Certsis a premium service offering a comprehensive collection of exam questions and answers for over 1400 certification exams. It is regularly updated and designed to help users pass their certification exams confidently.
Please contact info@Prep2Certs.com and we will provide you with alternative payment options.
You can by Contacting our sales team.