Important Workday-Adaptive-Planning Exam Questions

Answer: C

Explanation:

Assumption accounts in Workday Adaptive Planning are purpose-built for storing global constants --- such as inflation rates, tax rates, or standard multipliers --- that are referenced across multiple formulas and sheets. By design, Assumption accounts allow data entry at the Top Level (Only), meaning a single value is maintained centrally and referenced uniformly throughout the model. This aligns with best practices for model maintainability: rather than hard-coding values into individual formulas, a central Assumption account serves as the single source of truth. When the inflation rate changes, the administrator updates one cell, and all dependent formulas recalculate automatically. This eliminates version drift and ensures consistency across the entire model. Modeled accounts are used for row-based planning; Metric accounts display calculated KPIs but are not editable input stores; Custom accounts have different structural roles. Assumption accounts are foundational in Adaptive Planning's architecture and appear prominently in the Accounts configuration under Model Management. Reference: Workday Adaptive Planning --- Accounts Setup, Assumption Account Configuration, Model Management.

Answer: A

Explanation:

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: D

Explanation:

When a new Workday Adaptive Planning instance is initialized, the system automatically creates two default exchange rate types: Average and End of Month. The Average rate is typically used for translating income statement accounts (revenues and expenses), where the average exchange rate over a period better represents the economic reality of ongoing transactions. The End of Month rate is used for translating balance sheet accounts (assets, liabilities, equity), where the closing rate at period end reflects the current value of those balances. These two rate types correspond directly to standard financial accounting currency translation methodologies mandated by accounting standards such as ASC 830 and IAS 21. Historical and Budget rates are additional types that can be created manually but are not default system-generated types. Local and Corporate refer to currency designations, not exchange rate types. Actuals and Plan refer to version types. The Average and End of Month defaults align Adaptive Planning with standard multi-currency financial reporting requirements out of the box. Reference: Workday Adaptive Planning --- Currency Setup, Exchange Rate Types, Multi-Currency Configuration.

Answer: B

Explanation:

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

Explanation:

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.