A mobile allowance plan has a target amount of $150 per month. The new target amount will be $200 per month for employees using the plan.
Employees who currently have an override amount should retain their existing difference.
How will you update the plan target while maintaining current differences?
Correct Answer: D
In Workday, when updating allowance plan target amounts, administrators must carefully manage how the change impacts employees who are assigned override amounts. Overrides represent intentional deviations from the plan default, and preserving those differences is often a business requirement.
The Set Up Allowance Plan Adjustment task provides specific options for handling overrides. The option Adjust by Same Amounts for Employees Using Override increases each employee’s allowance by the same delta as the change to the plan default. In this scenario, the default increases from $150 to $200, a difference of $50. Employees with override amounts will also receive a $50 increase, thereby preserving their original variance from the default.
Selecting Adjust to New Defaults would eliminate the override difference by resetting employees to the new default amount, which contradicts the requirement. Removing or re-rolling out the plan introduces unnecessary disruption and risk.
Therefore, the correct approach is to use the Set Up Allowance Plan Adjustment task and select Adjust by Same Amounts for Employees Using Override, making option D correct.
What options are available when configuring a business process notification?
Correct Answer: D
When configuring Business Process Notifications in Workday, administrators can define the recipient based on a specific Workday Account. This allows precise targeting of individuals or security groups (e.g., HR Partner, Manager, or specific role-based accounts) who should receive the notification.
Option D is correct because ”Recipient based on Workday Account” ensures the system routes the notification to the appropriate user or group dynamically, based on the context of the business event. This is essential for process transparency and timely action.
Option A (Sender based on Workday Account) is incorrect — the sender is system-defined (”Workday Notification”), not configurable by user account.
Option B (On exit) and Option C (Trigger on In Progress) are not valid notification configuration options; triggers are defined by process status changes such as ”Awaiting Action,” ”Completed,” or ”Denied.”
Reference (Paraphrased Source):
Workday Pro HCM Core — Business Process Configuration Guide (2023R2), Section: ”Business Process Notifications and Recipient Configuration.”
What prevents a user from running a Workday Standard Reports report?
Correct Answer: D
In Workday HCM, the ability to run reports, including Workday-delivered standard reports, is governed by domain security, not by report writer or administrator roles. Domain security controls access to the data itself, and without access to the underlying domains referenced by a report, a user cannot run the report—even if the report is standard and delivered by Workday.
Standard reports are prebuilt and do not require report creation or modification privileges. Therefore, users do not need to be members of the Report Writer or Report Administrator security groups to run them. Those roles are only required for creating, copying, modifying, or administering reports—not for execution.
Additionally, access to a business process is unrelated to report execution. Business process security determines who can initiate or participate in transactions such as Hire or Termination, but it does not control visibility into report data.
Workday evaluates a user’s domain security policies at runtime to determine whether they can access the data objects used in the report. If the user lacks permission to one or more required domains, the report will either fail to run or return incomplete or restricted results. This applies equally to standard and custom reports.
From a Workday Pro HCM best-practice standpoint, ensuring users have the appropriate domain access—typically through role-based or user-based security groups—is the correct way to enable report execution. Report access groups alone are insufficient without the necessary domain permissions.
Therefore, the correct and Workday-verified reason a user cannot run a Workday Standard Report is that the user does not have access to the appropriate domain.
You want all managers to approve both hire details and proposed compensation. The consolidated approval chain step displays after Propose Compensation and the completion step, Review Employee Hire. What statement describes the action that happens next?
Correct Answer: C
Comprehensive and Detailed Explanation (Paraphrased from Workday Pro HCM Core — Business Process Configuration Guide 2023R2):
A Consolidated Approval Chain Step allows multiple approval actions within a business process to be combined into a single, streamlined approval task. However, this step must be the final step before the completion step in a business process.
If the Consolidated Approval Chain appears after the completion step, Workday will trigger a critical error because the step order violates the BP framework rules. The system expects the consolidated approval to act as the last step to ensure that all approvals are received before the event finalizes.
Therefore, Option C is correct — a critical error occurs because the Consolidated Approval Chain Step must immediately precede the completion step, not follow it.
Reference (Paraphrased Source):
Workday Pro HCM Core — Business Process Configuration Guide (2023R2), Section: ”Consolidated Approval Chains and Step Sequence Rules.”
You need to create a new supervisory organization and it needs to inherit attributes from an existing supervisory organization. What task do you use?
Correct Answer: D
Comprehensive and Detailed Explanation (Paraphrased from Workday Pro HCM Core — Organizations Setup and Management Guide 2023R2):
When creating a new supervisory organization that should inherit attributes such as staffing model, company, and cost center from an existing organization, you use the Create Subordinate task.
This task creates the new subordinate organization directly under a superior supervisory organization. It automatically copies inherited settings such as visibility, organization assignments, and staffing model, ensuring hierarchical alignment and simplifying setup.
Option B (Create Supervisory Organization) creates a brand-new top-level supervisory org without inheritance.
Option A (Assign Roles) only assigns role-based permissions after creation.
Option C (Assign Included Organizations) is used for related org relationships, not for hierarchical creation.
Thus, Create Subordinate is the correct task when the new org must inherit settings from a superior one.
Reference (Paraphrased Source):
Workday Pro HCM Core — Organizations Configuration Guide (2023R2), Section: ”Creating Subordinate Supervisory Organizations and Inherited Attributes.”
Prep2Certsis a premium service offering a comprehensive collection of exam questions and answers for over 1400 certification exams. It is regularly updated and designed to help users pass their certification exams confidently.
Please contact info@Prep2Certs.com and we will provide you with alternative payment options.
You can by Contacting our sales team.