As an implementation consultant, you have defined multiple grades for each job and position. While defining employment terms or assignments, users must be able to select a grade only from the list…

Mateus R.Apr 22, 2026

The answer is C. Think of PER_ENFORCE_VALID_GRADES like a bouncer at the door of a club, where the guest list is your defined grade list for each job or position. When that profile option is set to No at the site level, the bouncer goes home and lets everybody in, which is exactly why users are seeing all grades instead of just the valid ones tied to the job or position.

Imani T.Apr 8, 2026

The trick here is understanding what "enforce" actually means in context. PER_ENFORCE_VALID_GRADES being set to No means the system will still show grades tied to the job or position, but it won't stop you from picking something outside that list, so all grades stay selectable. Option E is the trap because people assume setting it to Yes is the problem, when Yes is actually what you WANT if you need to lock users down to valid grades only. PER_DEFAULT_GRADE_FROM_JOB_POSITION (Options A and B) is about defaulting a grade automatically, not restricting the list, so those are red herrings entirely. The answer is C, profile option PER_ENFORCE_VALID_GRADES at site level needs to flip to Yes to get the behavior the consultant is looking for.

Nadia M.Apr 18, 2026

PER_ENFORCE_VALID_GRADES at site level being No is exactly why grades are not filtered, so C.

Bao N.Apr 5, 2026

The trap here is B, because people see "set to No" and assume disabling something at site level explains why grades are not being restricted, but PER_DEFAULT_GRADE_FROM_JOB_POSITION is about defaulting a grade value, not about enforcing the valid grades list at all. C is the right answer because PER_ENFORCE_VALID_GRADES set to No at site level is exactly what causes the system to ignore the grade restrictions on the job or position and show all grades instead.