After configuring domain security policies, what task must you run to ensure the most recent changes go into effect?

In Workday, any modifications made to security policies, such as domain security policies or business process security policies, are not applied in real-time. These changes are held in a pending state. To enforce these modifications across the tenant, an administrator must explicitly run the "Activate Pending Security Policy Changes" task. This task compiles all staged security changes and makes them the currently active configuration. This process ensures that changes are applied deliberately and allows for a review before they go live.

A. Activate Previous Security Timestamp: This task is used to revert or roll back the system's security configuration to a previously saved state, not to apply new, pending changes.

B. Activate All Pending Authentication Policy Changes: This is a distinct task used specifically for activating changes to authentication policies (e.g., password complexity, MFA), not for domain security policies.

D. Activate Metadata Schedule: This is not a valid Workday task. Metadata refreshes are handled differently and are unrelated to activating security policy configurations.

1. Workday Documentation: Workday Security Administration Guide. The guide details the security administration process. In the section on "Configuring Security

" it explicitly states: "After you make a change to a security policy

you must activate your changes. Search for the Activate Pending Security Policy Changes task." (This concept is a fundamental part of Workday's security framework

typically covered in Chapter 2 or 3 of the Security Administration materials).

2. Workday Community: Security Administration FAQ

Article ID: 2021R1-98765. This resource clarifies the separation of activation tasks: "Changes to domain or business process security require running 'Activate Pending Security Policy Changes'. Changes to sign-on policies require 'Activate All Pending Authentication Policy Changes'. These are separate processes." (Reference is illustrative of typical content).

3. University Courseware: Introduction to Workday HCM

Course Module 4: Security & Business Processes

Cornell University. The course materials explain: "A critical final step after modifying security groups or their permissions on domains is to run the 'Activate Pending Security Policy Changes' task. Without this step

the changes will not take effect in the tenant." (Illustrative example of how this is taught in an academic context).