As a Lead System Architect at a multinational corporation, you are tasked with addressing significant...

Comprehensive and Detailed Explanation From Exact Extract:

Pega’s troubleshooting and performance optimization techniques, as taught in Pega Academy’sTroubleshooting Missionand thePega Certified Lead System Architect Study Guide, focus on identifying bottlenecks using tools like alerts, logs, and performance analyzers. Database-related delays require targeted diagnostics to isolate and resolve issues efficiently.

Option A (Correct): Reducing query-time alert thresholds (e.g., for DB-QUERY-TIME) helps identify slow or complex database queries that may cause delays. Pega’s Alert Log and Performance Analyzer (PAL) use these thresholds to flag problematic queries, enabling targeted optimization, as documented in thePerformance Troubleshootingmodule.

Option B (Incorrect): Raising the threshold for blob-size alerts (e.g., BLOB-SIZE) would reduce sensitivity to large case instances, potentially missing performance issues. Lowering the threshold is more appropriate to detect oversized blobs, per theDatabase Performanceguidelines.

Option C (Correct): Analyzing high-usage periods helps pinpoint when database delays occur, allowing the LSA to correlate alerts, logs, and system metrics (e.g., via Log Analyzer or AES) to specific times. This is a standard troubleshooting approach, as outlined in theTroubleshooting Mission.

Option D (Incorrect): Writing Pega logs to the database server is not recommended, as it increases database load and could exacerbate performance issues. Logs should be analyzed externally (e.g., via Pega Log Analyzer), per theLogging and Monitoringmodule.