C_SEC_2405 · Question #70
Under which of the following conditions can you merge authorizations for the same object during role maintenance? Note: There are 2 correct answers to this question.
The correct answer is A. The activation status of a manual authorization must match the status of the changed B. The activation status and the maintenance status of the authorizations must match. In SAP role maintenance (PFCG), the profile generator can merge duplicate authorization objects only under specific conditions related to how each authorization was created and whether it has been activated. Why A and B are correct: Option A is correct because when a manually…
Question
Under which of the following conditions can you merge authorizations for the same object during role maintenance? Note: There are 2 correct answers to this question.
Options
- AThe activation status of a manual authorization must match the status of the changed
- BThe activation status and the maintenance status of the authorizations must match.
- CThe maintenance status of the changed authorizations must match the status of a manual
- DThe activation status and the maintenance status of the authorizations must NOT match.
How the community answered
(32 responses)- A81% (26)
- C6% (2)
- D13% (4)
Explanation
In SAP role maintenance (PFCG), the profile generator can merge duplicate authorization objects only under specific conditions related to how each authorization was created and whether it has been activated.
Why A and B are correct: Option A is correct because when a manually created authorization and a changed (auto-generated then manually edited) authorization share the same activation status, the system recognizes them as compatible and allows merging. Option B is correct because when two authorizations share both the same activation status and the same maintenance status (e.g., both are manual, or both are standard), there is no ambiguity and merging is permitted - these are the two distinct gates the system checks.
Why C and D are wrong: Option C inverts the logic of A - it describes the changed authorization's maintenance status needing to match the manual authorization's status, which is not a defined merging condition; the relevant check is on activation status, not maintenance status in that pairing. Option D directly contradicts B - requiring statuses to not match would mean merging happens only when authorizations are incompatible, which is the opposite of how the system works.
Memory tip: Think of merging like merging lanes in traffic - cars (authorizations) can only merge when they're traveling at the same speed (activation status) and in the same type of lane (maintenance status). Mismatched conditions mean no merge, and Option D is the trick answer that flips the rule.
Topics
Community Discussion
No community discussion yet for this question.