PEGACPLSA23V1 Certified Pega Lead System Architecture (LSA) Exam 23

Comprehensive and Detailed Explanation From Exact Extract :

Pega’s security auditing, as taught in Pega Academy’s Security Mission and the Pega Certified Lead System Architect Study Guide , tracks administrative

events that impact application security, such as changes to policies, access controls, and user records, to ensure compliance and traceability.

Option A (Correct) : Changes to security authentication policies (e.g., SSO or LDAP configurations) are critical security administration events, as they affect user access. These are audited, per the Security Auditing module.

Option B (Incorrect) : Changes to Dynamic System Settings (DSS) typically affect system behavior, not security directly, and are not standard security administration events, as noted in the System Configuration guidelines.

Option C (Correct) : Changes to Attribute-Based Access Control (ABAC) policies and conditions modify data access rules, making them significant security events that are audited, per the ABAC Configuration section of Pega Community.

Option D (Correct) : Changes to operator records (e.g., updating roles or access groups) impact user permissions and are audited as security administration events, as documented in the Operator Management module.

Option E (Incorrect) : Changes to report definition filters affect reporting logic, not security, and are not typically audited as security events, per the Reporting Design module.

[:, Pega Academy:Security Mission(covers security auditing)., Pega Community:Security Auditing(details on audited events)., Pega Certified Lead System Architect Study Guide (v23): Section onSecurity Design(emphasizes auditing security changes)., ]

Comprehensive and Detailed Explanation From Exact Extract :

Pega’s class structure and specialization, as outlined in Pega Academy’s Data Modeling Mission and the Pega Certified Lead System Architect Study Guide ,

leverage inheritance to manage common and specialized rules efficiently. Subclassing is the preferred approach for scenarios requiring specialization within a single application, such as culinary specializations.

Option A (Incorrect) : Positioning Culinary, Baking, and Confectionery at the same hierarchical level with common rules in a work pool class is inefficient and violates Pega’s inheritance model. Common rules should reside in a parent class, not a separate work pool, per the Class Design module.

Option B (Incorrect) : Using separate rulesets for Baking and Confectionery separates logic but does not leverage class inheritance for rule resolution. Class- based specialization is more aligned with Pega’s design principles, as noted in the Ruleset Management guidelines.

Option C (Incorrect) : Creating separate top-level applications for Baking and Confectionery is overkill for specializations within a single domain. Application-level separation is suited for distinct business units, not specializations, per the Application Architecture module.

Option D (Correct) : Creating Baking and Confectionery as subclasses under the Culinary class allows common rules to reside in the parent (Culinary) and specialized rules in the subclasses. This leverages Pega’s pattern and directed inheritance for efficient rule resolution and scope definition, as documented in the Class Specialization section of Pega Community.

[:, Pega Academy:Data Modeling Mission(covers class inheritance and specialization)., Pega Community:Class Specialization(details on subclassing for rule scope)., Pega Certified Lead System Architect Study Guide (v23): Section onData Modeling(emphasizes hierarchical class design)., ]