A company is implementing field-level auditing in their application.

Comprehensive and Detailed Explanation From Exact Extract:

Pega’s field-level auditing, as described in Pega Academy’sPerformance Optimization Missionand thePega Certified Lead System Architect Study Guide, tracks changes to specific fields, which can impact performance if not managed carefully. The number of audited fields and modification frequency are key factors.

Option A (Correct): Auditing many fields increases database load due to additional history records, potentially impacting performance. This requires careful selection of audited fields, as documented in theField-Level Auditingsection of Pega Community.

Option B (Incorrect): Hosting on a high-performance server may mitigate performance issues but does not directly affect the auditing feature’s behavior. Auditing impacts are data-driven, per thePerformance Tuningmodule.

Option C (Incorrect): High user access affects overall system load but not specifically field-level auditing, which is tied to field changes, not user count, as noted in theAuditing Configurationguidelines.

Option D (Correct): Frequent modifications to audited fields generate numerous audit records, increasing database overhead and affecting performance. This is a significant concern, per theField-Level Auditingmodule.