Workday-Pro-Compensation Exam - Topic 1 Question 5 Discussion

Actual exam question for Workday's Workday-Pro-Compensation exam

Question #: 5
Topic #: 1

[All Workday-Pro-Compensation Questions]

When employees request a one-time payment for themselves, they have access to view and update the Gross Up and Send to Payroll checkboxes. Selecting these options could impact their payment.

How can you prevent employees from updating these options?

AConfigure Optional Fields for Request One-Time Payment to hide the fields.

BConfigure Optional Fields for Request One-Time Payment for Self to hide the fields.

CRemove Employee as Self from the Self-Service: Request One-Time Payment security domain.

DRemove Employee as Self from the Self-Service: Payroll security domain.

Show Suggested Answer

Suggested Answer: B

Employees requesting one-time payments for self may see sensitive options like Gross Up or Send to Payroll.

To prevent them from updating these fields, configure Optional Fields for Request One-Time Payment for Self and hide the checkboxes.

This limits their visibility and update access without affecting manager/HR workflows.

Why not the others?

A . Optional Fields for Request One-Time Payment Applies to manager/HR use, not self-service.

C . Remove Employee as Self from self-service comp domain Would block employees from initiating requests entirely.

D . Payroll security domain Payroll security doesn't control compensation request UI fields.

Workday Pro Compensation -- Configuring Optional Fields for Self-Service One-Time Payments.

by Dalene at Oct 04, 2025, 07:43 AM

Limited Time Offer

25%

Off

Get Premium Workday-Pro-Compensation Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Latanya

1 month ago

Agreed, A is my top choice.

upvoted 0 times

...

Wenona

2 months ago

Hiding fields is safer overall.

upvoted 0 times

...

Ettie

2 months ago

I just want to avoid errors.

upvoted 0 times

...

Marquetta

2 months ago

A is straightforward and effective.

upvoted 0 times

...

Tawanna

2 months ago

D limits employee control.

upvoted 0 times

...

Wenona

2 months ago

D is too extreme for me.

upvoted 0 times

...

Latanya

2 months ago

B still allows some access.

upvoted 0 times

...

Tawanna

3 months ago

Option B could work too.

upvoted 0 times

...

Ettie

3 months ago

But it prevents mistakes.

upvoted 0 times

...

Marquetta

3 months ago

C seems too restrictive.

upvoted 0 times

...

Ettie

4 months ago

I prefer option C.

upvoted 0 times

...

Latanya

4 months ago

I think option A is the best.

upvoted 0 times

...

Vannessa

4 months ago

B could work too, but A feels more straightforward.

upvoted 0 times

...

Cora

4 months ago

I’m not sure about option C, sounds a bit extreme.

upvoted 0 times

...

Gerald

4 months ago

Wait, can they really change those options? That seems risky.

upvoted 0 times

...

Cecilia

5 months ago

I vaguely recall that security domains are important for controlling what employees can see. Maybe option C is the best choice?

upvoted 0 times

...

Daniela

5 months ago

I’m a bit confused about the difference between the two optional fields options. Do they both affect the same settings?

upvoted 0 times

...

Tijuana

5 months ago

I think I remember something about configuring optional fields, but I'm not sure which option hides the checkboxes.

upvoted 0 times

...

Wilford

5 months ago

Hiding the fields is the way to go. Wouldn't want anyone to accidentally hit the "Gross Up" button and end up with a surprise bonus!

upvoted 0 times

...

Teddy

5 months ago

Totally agree, hiding those fields makes sense!

upvoted 0 times

...

Goldie

5 months ago

I think option A is the best choice.

upvoted 0 times

...

Jill

6 months ago

This question seems similar to one we practiced about security domains. I feel like removing access could be the right approach.

upvoted 0 times

...

Latanya

6 months ago

It hides the fields completely.

upvoted 0 times

...

Dante

6 months ago

Option B, no doubt. Can't trust those employees to not accidentally (or intentionally) mess with their pay!

upvoted 0 times

...

Delmy

6 months ago

Ah, the age-old battle between security and employee access. I'd say B is the safest bet.

upvoted 0 times

...

Cherry

7 months ago

Gotta love these tricky HR questions. I'm gonna go with D - keep those payroll fingers away from the controls!

upvoted 0 times

...

Vivan

7 months ago

Hmm, I'd go with C. Removing them from the security domain seems like a surefire way to lock it down.

upvoted 0 times

...

Queen

7 months ago

Option B seems like the way to go. Can't have employees messing with their own payments, right?

upvoted 0 times

...

I'm pretty confident that B is the right answer here. Hiding the fields on the "Request One-Time Payment for Self" form seems like the most targeted and effective way to prevent employees from updating those options.

upvoted 0 times

...

Von

7 months ago

Okay, let me think this through. We want to stop employees from being able to update the Gross Up and Send to Payroll checkboxes, but we still want them to be able to request a one-time payment for themselves. So I think B is the way to go - configure the optional fields to hide those specific fields.

upvoted 0 times

...

Willard

8 months ago

Hmm, I'm a bit confused. Do we want to completely remove the employee's ability to request a one-time payment for themselves, or just prevent them from updating those specific fields? I'm not sure if C or D is the better approach.

upvoted 0 times

...

Makeda

8 months ago

I think the key here is to prevent employees from accessing those specific fields. Option B looks like the best choice since it's targeted to the "Request One-Time Payment for Self" form.

upvoted 0 times