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

Answer : B

Workday Adaptive Planning supports alternate reporting hierarchies through the use of level dimensions and level attributes, which allow users to tag and classify levels according to groupings that exist in external systems of record such as Workday HCM or Workday Financial Management. This approach preserves the primary level hierarchy while enabling reporting along alternate dimensional structures without restructuring the core model. Level dimensions enable slice-and-dice reporting across dimensions that cross-cut the standard hierarchy, while level attributes allow metadata tagging of individual levels for grouping in reports and dashboards. Neither modifying the system of record nor creating parallel rollup structures represents a maintainable or scalable solution. The 'For reporting purposes only' checkbox applies to specific use cases but does not comprehensively support alternate hierarchy reporting across the model. Level dimensions and attributes are the recognized, official design pattern for multi-hierarchy reporting in Adaptive Planning. Reference: Workday Adaptive Planning --- Level Attributes, Level Dimensions, Alternate Hierarchies, Reporting Configuration.

Answer : B

When creating a standard sheet in Workday Adaptive Planning, a required structural step is to add accounts to a group. Standard sheets are organized by account groups, which serve as the organizational containers that determine which accounts appear on the sheet and in what order. Without at least one account group containing at least one account, the standard sheet cannot be saved or published, as it would have no content to display. Account groups function as logical sections of the sheet (e.g., 'Revenue Accounts,' 'Operating Expenses') and control the sheet's structure. Making accounts read-only is optional configuration that can be done after the sheet is created. Customizing level access is also optional and can be addressed post-creation. Adding custom dimensions is not a required step for standard sheets --- dimensions are primarily used in cube and modeled sheets. The mandatory creation requirement is the addition of accounts within an account group, which defines the sheet's core content and structure. Reference: Workday Adaptive Planning --- Standard Sheet Creation, Account Groups, Sheet Configuration.

Answer : A

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.

Answer : B

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.

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.

Answer : C

In Workday Adaptive Planning, before changing the default time stratum of an instance, all standard account data must be deleted. This is a prerequisite enforced by the system because the time stratum fundamentally defines how data is stored and aggregated across time periods. Standard account data is structured according to the current time stratum, and changing the stratum without clearing this data would create structural inconsistencies and orphaned data records that the system cannot reconcile. Once the data is deleted, the administrator can change the default time stratum and rebuild the time structure. This is why changing the default time stratum is considered a significant, typically one-time implementation decision that should be made before data is populated. Setting the stratum to a specific value, deleting the calendar, or appending the calendar are not prerequisites for this change --- the critical precondition is the deletion of existing standard account data. Reference: Workday Adaptive Planning --- Time Configuration, Default Time Stratum, System Setup Prerequisites.

Answer : B

In Workday Adaptive Planning standard sheets, the Level Availability setting controls whether an account is available for data entry (editable) or restricted to read-only access at each level. To make the Office Supplies account read-only for all levels, the administrator configures the Level Availability for that account to be read-only or unavailable across the entire level hierarchy. This setting overrides any level-specific edit permissions and ensures that regardless of a user's Edit access to a level, they cannot modify the Office Supplies account values on that sheet. Initial View controls the default display state of the sheet (collapsed/expanded). 'Customization for sub-levels' allows different configurations for child levels but does not enforce a universal read-only rule across all levels in a single setting. Account Groups organize accounts into sections within the sheet but do not control editability. Level Availability is the specific, purpose-built setting for controlling account-level read/write access within a standard sheet configuration. Reference: Workday Adaptive Planning --- Standard Sheet Configuration, Level Availability, Read-Only Account Settings.