The correct answer isC - Position Management.
In Workday,Position Managementis the staffing model used when an organization needs totrack headcount, vacancies, and time-to-fillfor each position individually. Each position represents a distinct job slot that must be filled by a worker, providing clear visibility into when a position is open, filled, or closed.
This model is ideal for organizations that require detailed tracking of resource allocation, workforce planning, and recruiting metrics such as"time to fill". Because each position must exist before a hire can occur, Workday automatically records thedate the position is openedand thedate it is filled, allowing accurate reporting on recruitment cycle times.
In contrast,Job Managementgroups workers under jobs rather than individual positions and does not provide vacancy-level tracking, making it unsuitable for time-to-fill analysis.
Reference:Workday Pro HCM -Staffing Models and Position Management Guide, "Comparing Position Management and Job Management Models."

The correct answer isC - Offers greater control on each position open within an organization.
ThePosition Managementstaffing model is designed for organizations that requireprecise headcount control and visibility into staffing levels. Each position represents a discrete role that must becreated, approved, and trackedbefore a hire occurs.
This model provides a high degree of control over:
* Vacancies and filled positions
* Position attributes (FTE, job profile, location, etc.)
* Time-to-fill metrics for open roles
Because every hire is linked to a specific position, administrators can effectively monitor workforce planning, budgeting, and resource allocation.
Reference:Workday Pro HCM -Staffing Model Fundamentals, "Benefits of Position Management."

By default, Workday restricts users to entering one one-time payment per event when the reason and effective date are the same. To support scenarios where multiple one-time payments are required-such as bonuses, awards, or stipends paid on different dates-the tenant-level setting Enable Multiple One-Time Payments must be enabled.
This configuration is found in Edit Tenant Setup - HCM and allows users to enter multiple one-time payment rows within the same event, even when the effective date and reason are identical.
Business process steps, eligibility rules, and UI help text do not control the system's ability to accept multiple one-time payments in a single transaction. Without this tenant setting enabled, Workday enforces a single- payment limitation.
Therefore, enabling Enable Multiple One-Time Payments is required, making option A correct.

In Workday HCM,allowance plan profilesare used to localize compensation amounts for specific employee populations based on eligibility criteria such as location. When an employee meets the eligibility for a plan profile, Workday defaults the amount defined in that profile.
However, when an employee doesnotmeet the eligibility criteria for any existing plan profiles, Workday defaults to thebase default valuedefined on the allowance plan itself. In this scenario, the default value is
$100 USD, and the available profiles only apply to employees in Toronto, Paris, and Sydney.
Since the employee is being hired inDublin, Ireland, they do not qualify for any of the defined profiles. As a result, Workday applies the plan's default value rather than a profile-specific amount.
Workday does not automatically convert currencies or default to zero unless explicitly configured to do so.
Therefore, the default amount remains $100 USD.
Options A and C incorrectly assume that Workday defaults to zero, which is not standard behavior. Option D applies only to Paris employees.
Thus, the correct answer is$100 USD, making option B correct.

In Workday HCM, hiring restrictions define the allowable values a manager can select when hiring into a position or job management organization. These restrictions are enforced strictly to ensure governance, compliance, and consistency in staffing decisions. When a value is explicitly restricted, only the values defined in the restriction are valid during the hire process.
In this scenario, the position has hiring restrictions configured for Location, allowing only New York and San Francisco. Although other attributes such as time type are not restricted and therefore remain flexible, location is explicitly constrained. When the manager attempts to hire a worker with the location set to London
, Workday prevents the transaction from continuing because London is not included in the allowed location values for the position.
The job profile requirement is met, as both the position and the hire specify Staff HR Representative, and the worker type also aligns with the restriction of Employee. The Time Type: Full Time does not cause an issue because time type is not restricted, meaning any valid time type can be selected.
Option A is incorrect because managers are allowed to specify values beyond the restricted fields, as long as they comply with any existing restrictions. Option B is unrelated to the scenario, as the issue is not related to hire reason configuration. Option D is incorrect because unrestricted fields do not block hiring.
From a Workday Pro HCM perspective, this scenario reinforces the importance of reviewing position hiring restrictions carefully. Any attempt to select a value outside a defined restriction-such as an unauthorized location-will result in the hire being blocked. Therefore, the correct answer is the manager cannot select London because it is not in the list of hiring restrictions for location.