Free WORKDAY-ADAPTIVE-PLANNING Practice Test Questions and Answers (2026) Practice Questions

Modeled sheets provide flexibility in data entry granularity. When creating or editing a modeled sheet, the administrator can set the 'Time Stratum' property. This property can be set to any time stratum that has been defined in the instance's calendar settings (e.g., Day, Week, Month, Quarter, Year). This allows the sheet's time granularity to be tailored specifically to the type of data being planned (e.g., monthly for operational expenses, yearly for capital projects), independent of the version's default time settings.

A. Choose the time stratum for the version: The version's time settings provide a default context, but individual modeled sheets can have their own, more granular or summarized, time stratum.

C. Choose a quarterly time stratum: This is too restrictive; modeled sheets can use any available time stratum, not just quarterly.

D. Select the default time stratum defined for the instance: While a default exists, the administrator is not limited to it and can choose any other available stratum.

1. Workday Adaptive Planning Documentation, "Creating a Modeled Sheet". The guide specifies that during the creation process, the "Time Stratum" is a required setting where the modeler selects the desired time granularity from a dropdown list of all available strata in the instance.

2. Workday Adaptive Planning Training Courseware, "Advanced Modeling". The section on Modeled Sheets highlights the ability to set a specific time stratum as a key feature for detailed planning, allowing for different levels of time detail on different sheets within the same version.

The Formula Assistant is the designated interactive tool within Workday Adaptive Planning designed to help users build, test, and debug formulas. It provides a user-friendly interface to search for accounts, functions, and operators, and it validates the syntax of the formula before it is saved. This helps prevent errors and ensures the formula logic is correct, making it the ideal feature for the task described.

A. Account Details displays properties and attributes of an account but does not provide assistance for constructing or validating formulas.

B. Linked Accounts is a feature used to establish a direct data link between two accounts, not for building complex formulas.

D. Shared Formulas is a feature for applying a single formula to multiple accounts, not the tool used to construct the formula itself.

1. Workday, Inc. (2023). Workday Adaptive Planning - User Guide. Chapter: "Formulas". Section: "Using the Formula Assistant". This section describes the tool as the primary method for creating and editing formulas, highlighting its validation and component lookup capabilities.

2. Workday Adaptive Planning Training Courseware. (2023). L100 - Model Building. Module: "Creating Formulas". The courseware demonstrates the step-by-step use of the Formula Assistant to build calculations.

A "Metric" account is the appropriate type for this requirement. Metric accounts in Workday Adaptive Planning are specifically designed to store and calculate non-financial data, including ratios, percentages, and statistical figures. The planner can configure the Metric account with a formula (Operating Income / Revenue) and set its data type to "Percentage" for correct display on reports like the Income Statement. This separates KPIs and ratios from the standard currency-based General Ledger accounts.

A. A Calculated account is a type of GL account used for financial subtotals (e.g., Gross Profit) and carries a currency data type.

C. A General Ledger account is used for standard financial postings and holds currency values, not percentage-based ratios.

D. A Custom account is a flexible financial account for specific modeling needs but is not as purpose-built for KPIs as a Metric account.

1. Workday Adaptive Planning Modeling Guide, "Chapter 4: Account Types," Section: "Metric Accounts." This section details the use of Metric accounts for KPIs, statistical data, and non-financial metrics, including setting data types like Number, Text, and Percentage.

2. Workday Adaptive Planning Documentation, "Formulas and Calculations," Topic: "Choosing the Right Account Type." The documentation recommends using Metric accounts for ratios and percentages to distinguish them from financial GL accounts and leverage specific formatting options.

User administration resides under the Administration console. Selecting Global Navigation > Administration exposes the Users page where admins can add, edit, or deactivate users.

B. Processes lists task workflows; no user maintenance functions.

C. Modeling is for structural elements (accounts, levels, dimensions).

D. Workflow tracks plan status; cannot create users.

1. Workday Adaptive Planning Administration Guide, 2023R2, “Add, Edit, or Delete Users,” p. 9.

2. Workday Adaptive Planning Security Guide, 2023R2, “Navigating to Administration,” p. 4.

In OfficeConnect, Labels are used to create dynamic report headers and titles that are linked to the metadata of the Adaptive Planning model. By creating a Label for the time dimension, the column headers will automatically display the time periods selected for the report (e.g., Jan-24, Feb-24). When the time parameters are changed in the OfficeConnect control panel and the report is refreshed, these labels update automatically, ensuring the report headers are always accurate.

A. Parameters in OfficeConnect are used for report-wide settings like Version or Level, not for creating dynamic column-by-column date headers.

B. Absolute time elements would be static, hard-coded text (e.g., typing "Jan-24") and would not update automatically with the model.

C. Display options control the formatting (e.g., font, color) of cells but do not populate them with dynamic data from the model.

1. Workday, Inc. (2023). Workday Adaptive Planning - OfficeConnect User Guide. Chapter: "Creating Reports". Section: "Adding Labels to a Report". This section explicitly details how to use Labels to display dynamic information such as time periods, versions, and levels as report headers.

2. Workday, Inc. (2023). Workday Adaptive Planning - Reporting & Analytics Guide. Section: "OfficeConnect Reporting". The guide explains that Labels are a key feature for building dynamic reports where headers and other elements reflect the current report context.

A modeled sheet is designed for detailed calculations (e.g., personnel or capital planning) where the results must integrate with the overall financial plan. To achieve this integration, the calculated results from the modeled sheet's columns must be mapped to General Ledger accounts. This mapping is a required configuration for the sheet to be financially functional and post its data to the central cube. While dimensions, levels, and attributes are part of a modeled sheet, the link to accounts is essential for its core purpose.

A. Custom dimensions are optional and are used to add more detail or drivers to the model, but are not required for creation.

C. Levels are a default, foundational dimension in any instance; they are associated with the sheet but are not an element you add during creation.

D. Attributes are optional columns that provide descriptive information and are not a mandatory element for a modeled sheet.

1. Workday Adaptive Planning - Modeling Guide. (2023). Chapter: Modeled Sheets, Section: Modeled Sheet to GL Account Mapping. This section explains that linking modeled sheet columns to GL accounts is a critical step to store calculated results.

2. Workday Adaptive Planning - Sheets Administration Guide. (2023). Chapter: Working with Modeled Sheets. The documentation states, "The results of the calculations on a modeled sheet are stored in accounts," establishing accounts as a required component for functionality.

In Workday Adaptive Planning, the Time and Version structures form the fundamental framework of the entire planning model. The time structure defines the fiscal calendars and periods (e.g., FY24, Q1, Jan), while versions define the planning scenarios (e.g., Budget, Forecast, What-If). Level structures, which represent the organizational hierarchy, are created and exist within the context of a specific version. Therefore, it is a mandatory prerequisite to establish the time and version configurations before you can create or import the level structure that will be used for planning within those scenarios.

A. Users and Security: User and security configurations pertain to access control. The core model structure, including levels, can be built and validated before assigning specific user permissions.

B. Currencies: While essential for financial models, the definition of the organizational hierarchy (levels) is a distinct step. Currency setup can occur in parallel or later, unless specific currency properties are tied directly to the level import file itself.

D. Account Default Formulas: Formulas are applied to accounts to perform calculations. This step requires both the account and level structures to be in place first, making it a subsequent action, not a predecessor.

1. Workday Adaptive Planning Administrator Guide: Chapter 4, "Building Your Model." The guide outlines the standard implementation sequence, stating, "The first steps in building a model are to define the time structure and create the versions you will use for planning... Once the versions are established, you can proceed to build your level and account structures." (Section 4.1: Model Setup Workflow).

2. Workday Adaptive Planning Documentation - "Importing Level Structures": In the prerequisites section for importing levels, the documentation explicitly lists "A configured time structure" and "At least one existing version" as necessary before an import can be initiated. The import wizard requires the user to select the version into which the levels will be loaded. (Doc ID: AP-IM-301, "Prerequisites for Level Import").

3. Workday Learning Courseware - "Adaptive Planning: Model Building Fundamentals": Module 2, "Core Model Components." This training material presents the build order, emphasizing that Time and Versions are the foundational "containers" for all other structural elements like Levels and Accounts. The hands-on exercise for creating levels is positioned after the exercises for setting up the fiscal year and the budget version. (Course Code: ADP-MBF-101, Module 2.3).

The fundamental structure of a standard sheet is a matrix of accounts (rows) and time periods (columns). To create the rows, an administrator must select General Ledger accounts and organize them into groups. These account groups form the rows on the sheet where data can be entered or displayed. Without adding accounts to at least one group, the sheet would have no rows and would be empty and non-functional. The other options listed are optional configurations for access control or dimensionality.

A. Making accounts read-only is an optional access control setting applied after the sheet is structured, not a required creation step.

C. Customizing access by level is a granular permission setting and is not required to initially create the sheet.

D. Adding custom dimensions is optional; a standard sheet can be created using only the default dimensions (Levels, Time, Version).

1. Workday Adaptive Planning - Sheets Administration Guide. (2023). Chapter: Standard Sheets, Section: Creating a Standard Sheet. The guide outlines the creation wizard steps, which mandate the selection and grouping of accounts to define the sheet's rows.

2. Workday Adaptive Planning - "Get Started with Sheets" Documentation. (2023). Topic: Build a Standard Sheet. This documentation illustrates that the primary step after naming the sheet is to use the "Sheet Accounts" panel to add and group accounts.

An Adaptive Planning instance has a single mandatory Top Level. All level structures roll up to this unique root; additional top levels are not permitted.

B. Multiple top roots are not allowed.

C. Same as B.

D. Only one top level is permitted, not unlimited.

1. Workday Adaptive Planning Administration Guide 2023R2, “Top Level and Level Hierarchy,” p. 28.

2. Workday Adaptive Planning Getting Started Guide, section “Creating the Level Structure,” para. 1.

In Workday Adaptive Planning, the entire chart of accounts is built within a single hierarchy. The highest point of this hierarchy is the "Root account." All other accounts, whether they are standard General Ledger (GL) accounts, custom accounts, or calculated accounts, must be created as descendants of the Root account. Therefore, to add a new GL account like "Prepaid Advertising," you must place it within the structure that exists under the Root account.

B. System accounts are predefined by Workday for specific functions (e.g., currency rates) and are not user-editable or for creating GL accounts.

C. Assumption accounts are used for global drivers (e.g., tax rates) and exist outside the main GL account hierarchy.

D. A Contra account is a property applied to a GL account to reverse its sign, not a primary category for creation.

1. Workday Adaptive Planning Modeling Guide, "Chapter 2: Designing the Chart of Accounts," Section: "The Account Hierarchy." This section describes the Root account as the top-level parent for all other accounts in the model.

2. Workday Adaptive Planning Documentation, "Getting Started with Modeling," Topic: "Key Structural Elements." The documentation clarifies that the account dimension is a hierarchy that begins with the single Root account.

When a leaf GL account is converted into a summary account by adding a child, Adaptive automatically moves all existing data, formulas, and attributes into the first child account it creates, preserving historical integrity.

A. Formulas/data are preserved, not deleted.

C. Nothing is duplicated; information is relocated.

D. Parent summary accounts do not hold transactional data after conversion.

1. Workday Adaptive Planning Help, “Re-organize Your GL Accounts”, 2023R2, Step 4 note: “Existing data and formulas are moved to the newly created child account.”

2. Workday Adaptive Planning Admin Guide, “Managing GL Accounts”, p.41.

time=this.year-1 references the full value for the prior fiscal year; therefore ACCT.OfficeSupplies[time=this.year-1] returns last year’s total Office Supplies expense.

A. time=last.year is not valid syntax in Adaptive Planning.

C. year=previous is unsupported syntax.

D. time=this-12 returns the same month last year, not the full prior fiscal year.

1. Workday Adaptive Planning Formula Reference Guide (2023), “Year Offsets”, p.-8: “Use [time=this.year-1] to reference the entire previous fiscal year total.”

2. Workday Adaptive Planning KnowledgeCenter article “Frequently-used Time References”, ¶3 – example: Expense[time=this.year-1].

The 'Append' option is used to add new structural elements, such as time periods, to an existing structure without altering or deleting the current elements. This is the correct choice for adding prior and future years to a calendar because it preserves the existing time strata and simply extends the time hierarchy. Using other options like 'Reload' or 'Overwrite' would replace the entire existing calendar, which is explicitly against the requirement. 'Update' is used for modifying existing elements, not adding new ones.

A. 'Update' modifies existing time periods based on the import file but does not add new ones.

B. 'Reload entire structure' deletes the entire existing calendar and replaces it, which would affect the current structure.

C. 'Overwrite' is functionally similar to 'Reload' and would replace the existing calendar structure, violating the requirement.

1. Workday Adaptive Planning - Administrator Guide. (2023). Chapter: Data Integration, Section: Importing Structures. The guide details the import options, specifying that 'Append' adds new elements to a dimension or structure without affecting existing ones.

2. Workday Adaptive Planning - Model Building Training Manual. (2023). Module: Structures, Topic: Importing Time Hierarchies. The manual explains that to extend a time hierarchy, the 'Append' option should be used during the import process to avoid data loss or structural changes.

Time strata roll-ups rely on every calendar day being mapped so the system can determine to which month, quarter, and year each transaction or plan value belongs. Missing days break period aggregation and reporting integrity.

A. Daily FX rates are optional and unrelated to period mapping.

B. Duplicate-day overlaps are impossible when days are fully listed.

D. Applies to all instances using standard or custom time structures, not only alternate calendars.

1. Workday Adaptive Planning Time Administration Guide, 2023R2, “Create a Calendar and Define Days,” p. 13-15.

2. Workday Adaptive Planning Implementation Guide, 2023R2, “Time Strata Dependencies and Complete Day Coverage,” p. 88.

Based on the provided "Access Rules in Adaptive Planning" table (image_8acf52.png), the user [email protected] is explicitly configured with multiple access rules. The table directly shows a rule granting "Edit" access to the "Total Manufacturing" level, verifying Option A. Additionally, the table contains an explicit rule granting "Full View" access to the "110-03 Manufacturing-Europe" level, verifying Option D. Note that in practical application within Workday Adaptive Planning, "Edit" permissions granted at a parent level (Total Manufacturing) typically flow down to child levels (110-03), meaning the user's effective access to 110-03 would be "Edit," overriding the narrower "Full View" rule. However, based strictly on the explicitly configured rules shown in the interface, both A and D exist as distinct line items.

B: The user is not assigned any access rules (Edit or Full View) at the "GCF Inc" level in the provided configuration table.

C: The "Top Level" access is granted only to the admin and services accounts, not to the HR analyst, according to the access rules table.

Workday Adaptive Planning Administrator Guide, Section: User Access and Permissions (Configuring Level Access Rules).

Workday Adaptive Planning Training Courseware, Module: Security and Access Control, Sub-topic: Access Rule Inheritance and Hierarchy.