โ† All CSA Flashcard Decks

Performance Monitoring Flashcards

7 cards from real CSA practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Performance Monitoring flashcards as text
  1. Which Pega workspace lets an administrator monitor requestors, background processing, and queue processors across nodes?

    Answer: Admin Studio

    Admin Studio provides system-level monitoring of nodes, requestors, and background processing.

  2. Alert PEGA0035 indicates which condition?

    Answer: A Page List property contains more elements than the configured threshold

    PEGA0035 warns that a Page List has grown beyond the allowed number of elements, risking memory issues.

  3. A team wants to identify which specific rules consume the most CPU time within a single requestor's thread. Which tool gives a rule-by-rule execution breakdown?

    Answer: Performance Profiler

    Performance Profiler records detailed per-rule execution timing for a thread.

  4. Why should the Performance Profiler not be left running in a production environment?

    Answer: It adds significant overhead and generates large output

    Profiling captures detailed data for every rule, which slows the system and produces large files.

  5. What is the main benefit of using a data page instead of repeatedly running the same lookup in each activity?

    Answer: Data pages cache results, reducing redundant database or service calls

    Data pages load data once and reuse it based on refresh strategy, reducing repeated I/O.

  6. Where can a lead developer review guardrail warnings and the compliance score for an entire application?

    Answer: Application Guardrails landing page

    The Application Guardrails landing page summarizes warnings and compliance score across the application.

  7. PAL shows a high number of database requests for a simple screen that displays the same reference data several times. What is the most likely design issue?

    Answer: The reference data is reloaded instead of being sourced from a cached data page

    Repeated database requests for the same reference data suggest it should be loaded once into a reusable data page.