What factors should be considered when managing access permissions? (Select two.)

Question

Options

• AUser's group and team assignments
• BWorkfront system status hierarchy
• CActive projects in the portfolio
• DExternal storage configurations

• A
  71% (47)
• C
  11% (7)
• D
  18% (12)

Explanation

Managing access permissions requires knowing who needs access and what level they should have within the system's authority structure.

Why A and B are correct:

• A (User's group and team assignments) determines what resources a user should access based on their role and organizational membership - granting permissions to a group automatically cascades to all members, making this a foundational access control factor.
• B (Workfront system status hierarchy) governs what actions users can take at different workflow stages; certain statuses restrict editing or visibility, so the hierarchy directly shapes what access is appropriate.

Why the distractors are wrong:

• C (Active projects in the portfolio) describes project activity, not a factor in defining who gets access to what - portfolio content doesn't drive permission logic.
• D (External storage configurations) relates to integration and infrastructure setup, not to the rules governing user access rights within the system.

Memory tip: Think "Who + Where in the hierarchy" - Group assignments tell you who the user is organizationally (A), and the status hierarchy tells you where in the workflow they operate (B). Both together define appropriate access.

No community discussion yet for this question.