PEGACPSA88V1-QUESTION practice question 11 of 15

An internal application currently grants employees access to one of four personas Admin. Author. User, and Manager A new system administrator who joins the company requires all the access of the Admin persona but only some of the reporting features are available to the Author persona How do you satisfy this security requirement? Available Choices (select all choices that are correct)

Full set: 82 questions
Answer options
A: Add the system administrator to both the Author persona and Admin persona.
B: Update the Admin persona to include the required access.
C: Create a new SysAdmin persona with the required access. Correct answer
D: Add the analyst to the Author persona.
Correct Answer:
C. Create a new SysAdmin persona with the required access.
Explanation

The most appropriate and secure method is to create a new persona specifically for this role. The new system administrator has a unique set of responsibilities that combines permissions from two different existing personas. Creating a new SysAdmin persona allows for the precise granting of necessary permissions (all of Admin and specific reports from Author) without altering the security configuration for other users. This approach adheres to the principle of least privilege and ensures the security model remains clean, maintainable, and scalable for future needs.

Why Incorrect

A. Add the system administrator to both the Author persona and Admin persona. This grants all permissions of the Author persona, not just some reporting features, violating the principle of least privilege.
B. Update the Admin persona to include the required access. This would grant unnecessary permissions to all other users assigned the Admin persona, creating a security vulnerability.
D. Add the analyst to the Author persona. This option fails to provide the required Admin-level access and incorrectly identifies the role as an "analyst." ---

References

1. Pega Academy, Certified Pega System Architect (CPSA) 8.8 Mission, "Securing an application" module.

Reference Section: In the "Personas and access groups" topic, the courseware explains that a persona represents a specific type of user. When a new user type with unique access requirements is identified, the standard practice is to create a new persona and a corresponding access group to encapsulate those requirements. This directly supports creating a new SysAdmin persona.

2. Pega Documentation, "Personas"

Reference Section: The documentation states, "Personas are a critical component of a user-centered application design because they define the user roles that interact with your application." It further clarifies that personas are used to design user experiences, including what data they can view and actions they can perform. Creating a new persona for the system administrator role aligns with this official guidance.

3. Pega Documentation, "Creating an access group"

Reference Section: This document details that an access group defines the permissions for a group of users. It states, "An access group is an instance of the Data-Admin-Operator-AccessGroup class. An access group specifies a Pega Platform application, a primary access role, and a portal layout for a user." To satisfy the unique requirement, a new access group would be created for the new SysAdmin persona, combining the necessary access roles. Modifying existing access groups (as suggested in option B) is discouraged for one-off requirements.

Scroll to Top