Workday Pro Adaptive Planning Certification Workday-Adaptive-Planning Exam Questions

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.

Answer : C

In Workday Adaptive Planning, the time calendar configuration requires that every day of the year be accounted for within the defined time structure, even when the lowest planning stratum is Month rather than Day. The system uses days as the foundational unit to determine how each month, quarter, and year maps to the calendar. If days are missing or gaps exist in the calendar, the system cannot correctly associate time periods, which can result in data alignment issues, incorrect period boundaries, and formula miscalculations. This is a setup requirement to ensure the time structure is complete and unambiguous --- the system needs to know definitively that, for example, January contains days 1--31 and February begins on day 32. This is not related to daily exchange rates (which are handled separately) or alternate reporting calendars. Ensuring complete day coverage is a foundational time configuration step in the Adaptive Planning implementation methodology. Reference: Workday Adaptive Planning --- Time Configuration, Calendar Setup, Time Stratum Definition.

Answer : A

In Workday Adaptive Planning's Workflow (Process Tracker), the Reject action is used by a manager or approver to send a submitted budget back for revision. When a Reject action is performed, the system unlocks the budget data for all child levels beneath the rejected level, returning edit access to the planners at those levels so they can make corrections and resubmit. This is the correct mechanism for sending work back down the approval chain --- the Reject action specifically restores editability to the child levels that had been locked when the budget was submitted. Recall is an action that allows a planner to withdraw their own submission before it has been approved, unlocking their own level's data. Submit locks the data at the current level and sends it up the approval chain. Approve finalizes the submission and may lock data at the parent level. The Reject action's specific function of unlocking all child levels is fundamental to the iterative budget revision process in Adaptive Planning's workflow. Reference: Workday Adaptive Planning --- Workflow, Process Tracker, Reject Action, Budget Approval Process.

Answer : B

In Workday Adaptive Planning, when a sub-account (child account) is created beneath an existing General Ledger account, the system converts the parent account into a rollup account. As part of this structural transformation, all existing data and any formulas that were previously stored in the parent Inventory account are automatically migrated to the newly created child account. The parent then becomes a rollup that aggregates the values of its children. This behavior ensures no data loss during model restructuring. The rationale is that rollup accounts do not hold direct data --- only leaf accounts (bottom-level accounts without children) can contain input values or formulas. Therefore, the system must relocate the data to maintain model integrity. Administrators should be aware of this behavior before creating sub-accounts in live environments, as it directly affects reporting and formula references. Existing reports may need to be updated to reflect the new account reference. Reference: Workday Adaptive Planning --- Chart of Accounts, Account Hierarchy, Sub-Account Creation Behavior.

Answer : A

Reviewing the access rules table displayed in the scenario, hr@wdayptnrgcf.com is assigned multiple access rules: Full View to 410-01 IT, Full View to 110-03 Manufacturing-Europe, Edit to Total G and A, Edit to Total Manufacturing, and Edit to Total Sales and Mkt. In Workday Adaptive Planning, when a user is granted access to a parent level such as Total Manufacturing with Edit permissions, that access cascades to all descendant levels beneath it --- including 110-01 Manufacturing-USA, 110-02 Manufacturing-Canada, and 110-03 Manufacturing-Europe. The question asks what access the HR analyst has, and among the options presented, 'Edit access to the Total Manufacturing level' is the correct characterization of their most significant structural permission. Full View to GCF Inc or Top Level is not listed in the rules. The access configuration demonstrates a deliberately scoped, multi-level permission set typical in departmental HR planning scenarios. Reference: Workday Adaptive Planning --- Security Configuration, Level Access Rules, Edit vs. Full View Permissions.

Answer : B

In Workday Adaptive Planning, Assumption accounts are configured within the Model Management section of the Modeling area. The precise navigation path is: Global Navigation menu > Modeling > Model Management > Accounts > Assumptions. Within Accounts, the system presents different account type categories, including GL Accounts, Metric Accounts, and Assumption Accounts. Selecting Assumptions allows administrators to create, edit, and manage global Assumption accounts that store planning constants such as inflation rates, tax rates, and other shared variables. The Administration path leads to user management and system settings --- not model configuration. There is no direct 'Assumptions' link in the Global Navigation menu. The 'Model Overview' submenu does not contain the Accounts configuration; Model Overview provides a structural summary of the model. Model Management > Accounts is the authoritative path for all account type configurations, including Assumptions. Reference: Workday Adaptive Planning --- Modeling Navigation, Model Management, Assumption Account Setup.

Answer : C

In Workday Adaptive Planning standard sheets, cell background colors communicate the editability status of each cell to the user. A grey cell background indicates that the cell is read-only --- it may contain a calculated value from a formula or display a rolled-up result, but the user cannot directly enter or modify data in that cell. Read-only cells appear grey to clearly differentiate them from white/editable cells, providing instant visual feedback about where data entry is permitted. This applies to cells that contain shared formulas, cells that are restricted by the sheet's Level Availability configuration, and cells that display rollup calculations. A white cell background indicates an editable cell where a user can enter values. Blue or colored cell backgrounds may indicate other states depending on configuration. Errors in cells are typically displayed with error text rather than a grey background. Rollup accounts do appear grey, but the grey color specifically means read-only, which is a broader category. Reference: Workday Adaptive Planning --- Standard Sheet Interface, Cell Color Coding, Read-Only vs Editable Cells.