Pass the Workday Adaptive Planning Workday-Adaptive-Planning Questions and answers with ExamsMirror

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.

In Workday Adaptive Planning, when an account is deleted from the model, all associated formulas and data stored in that account are permanently and irreversibly deleted across all versions and all levels. There is no automatic transfer, reassignment, or archiving mechanism. The system does not migrate data to sibling accounts or parent rollups upon deletion. This is a critical and irreversible action — once the Rent account is removed, its historical actuals, plan data, and any formulas are permanently lost from the model. This behavior underscores the importance of data backup and version control before performing structural changes. Administrators should export or archive data before deleting accounts. The rollup account Total Operating Expenses will continue to function but will now only aggregate the remaining child, Salaries. Any reports or dashboards referencing the deleted Rent account will return errors or blank values. Reference: Workday Adaptive Planning — Account Management, Account Deletion Behavior, Model Maintenance Best Practices.

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 refere nces in Adaptive Planning. Reference: Workday Adaptive Planning — Time Modifiers, Prior Year References, Formula Syntax Guide.

A modeled sheet is the appropriate design for detailed travel expense planning because it is architected to capture granular, row-level data where each row represents a discrete planning record — in this case, an individual trip. Modeled sheets support custom columns (accounts) such as destination, travel dates, estimated cost, level assignment, and dimension values, enabling planners to build detailed itinerary-level budgets. The data aggregates upward to summary levels for inclusion in corporate reporting. This meets both requirements: detailed planning visibility for Finance and individual planner completion per forecast cycle. A standard sheet captures aggregate monthly amounts by level but lacks the row-level granularity needed for trip-by-trip detail. A standard sheet with a historical formula is a top-down estimation approach, not a detailed planning model. A cube sheet with assumption-based calculation is a statistical model, not a detailed record-level capture. The modeled sheet's row-based architecture is specifically designed for this class of detailed operational planning. Reference: Workday Adaptive Planning — Modeled Sheets, Sheet Design Patterns, Travel Planning Use Case.

In Workday Adaptive Planning, a Parameter is the report design feature that enables each user running a report to make interactive selections — such as choosing their specific department (level) — at the time they run the report. Parameters create dynamic input prompts that appear when a report is executed, allowing users to select from available levels, versions, time periods, or other report axes based on their access permissions. This is ideal for a shared matrix report used by multiple departmental managers: each manager opens the same report but selects their own department from the Parameter prompt, receiving a personalized view of their expenses without requiring separate reports per manager. Filters apply static, pre-set conditions that are fixed by the report designer and are not adjustable by end users at runtime. Drill Down Choices enable hierarchical data exploration within a report but do not control the initial selection scope. Manage Hierarchy is not an interactive parameter feature. Parameters are the official mechanism for enabling user-driven, runtime report customization in Adaptive Planning reporting. Reference: Workday Adaptive Planning — Matrix Reports, Parameters, Report Design, Interactive Reporting.

The issue in the original formula is that ACCT.Lookups.Rate[Level=TopLevel(-)] retrieves the rate for all Product dimension values aggregated at the top level, rather than the rate specific to each individual Product dimension value being calculated. When the rate reference does not specify the Product dimension modifier, it pulls the aggregate (summed or unfiltered) rate value, resulting in inflated multiplication results. The corrected formula ACCT.Sales.Units * ACCT.Lookups.Rate[Level=TopLevel(-), Product=this] adds the 'Product=this' modifier, which instructs Adaptive Planning to look up the rate for the same Product dimension value as the current row being calculated. The 'this' keyword is a dynamic reference that matches the current dimension context. Level=TopLevel(-) correctly retrieves the globally-entered assumption rate (entered once at the top level), while Product=this ensures the rate corresponds to the specific product being evaluated. Without the Product=this modifier, the formula aggregates across all product rates, causing inflated results. Reference: Workday Adaptive Planning — Cube Sheet Formulas, Dimension Modifiers, 'this' Keyword, Level Modifiers.

The Contributor permission set template in Workday Adaptive Planning is specifically designed for users who need to enter budget data into planning sheets while also being able to view reports and dashboards. Contributors can add and modify values in sheets they have access to, which satisfies the requirement to add values to existing plan estimates. They also receive read access to reports and dashboards, fulfilling the contextual visibility requirement. The Power User template grants broader administrative capabilities that exceed what a standard budgeter requires. View Only limits users to read-only access with no data entry capabilities, making it inappropriate for budget input. Implementor is an elevated administrative role for system configuration and model building. The Contributor template is the optimal baseline because it is scoped precisely to the data entry and reporting visibility functions described, and it can be further refined by the administrator to limit access to specific levels or sheets. Reference: Workday Adaptive Planning — Security and Permission Sets, User Roles, Contributor Template Configuration.

In Workday Adaptive Planning, the recommended best practice for division operations in formulas is to use the built-in div() function rather than the forward slash (/) operator. The div() function provides division with safe handling of zero denominators — if the denominator is zero, div() returns zero instead of throwing an error, which prevents formula errors from propagating through the model. The correct formula div(ROW.BonusInput, 12)*(ROW.PartialHeadcount) first divides the bonus input by 12 using the safe div() function, then multiplies the result by the partial headcount using standard multiplication. Option B incorrectly places the multiplication inside the div() function, changing the order of operations. Option C uses the division operator (/) which is not recommended as it lacks zero-denominator protection. Option D incorrectly prefixes ROW accounts with ACCT., which is the wrong prefix for personnel sheet row references — ROW. is the correct prefix. Using div() with proper ROW. references is the authoritative Adaptive Planning formula pattern for this calculation. Reference: Workday Adaptive Planning — Formula Syntax, div() Function, Personnel Sheet ROW References.

In Workday Adaptive Planning, the 'Change Dimensions' toolbar option on a cube sheet allows end users to interactively modify which elements are displayed on the vertical (row) and horizontal (column) axes. This feature provides analytical flexibility, enabling users to pivot the view of the cube sheet — for example, moving a dimension from rows to columns, adding or removing dimensions from the view, or swapping the axis orientation. This is particularly valuable for ad hoc analysis where users need to explore data from different dimensional perspectives without requiring an administrator to reconfigure the sheet. 'Reset to Default View' returns the sheet to its administrator-defined default layout. 'Sheet Properties' contains configuration settings for the sheet's structural properties, not axis manipulation. 'Dimensions, attributes, and levels' may describe elements within the sheet but is not the specific toolbar option for axis management. 'Change Dimensions' is the dedicated interactive tool for axis manipulation in cube sheets. Reference: Workday Adaptive Planning — Cube Sheets, Change Dimensions, User Interaction, Axis Configuration.

The requirement specifies using the average monthly consulting expense from last year (total prior year divided by 12) then multiplying by (1 + inflation rate). The formula div(ACCT.ConsultingExpenses[time=this.year-1],12)*(1+ASSUM.Global_Inflation_Rate) correctly captures this: [time=this.year-1] retrieves the full prior year total, div(...,12) divides by 12 to calculate the average monthly value, and *(1+ASSUM.Global_Inflation_Rate) applies the inflation adjustment. Option A [time=this-12] references the same month from one year ago — a specific month's value, not an annual average. Option C omits the prior year time reference, using the current account value rather than last year's data. Option D retrieves the full prior year total without dividing by 12, which would apply inflation to an annual total rather than a monthly average. The combination of the annual prior year reference, division by 12, and the inflation multiplier makes Option B the precise implementation of the described estimation strategy. Reference: Workday Adaptive Planning — Time Modifiers, div() Function, Inflation Formula Patterns.