You are a Lead System Architect working on a booking application for a travel agency.

Comprehensive and Detailed Explanation From Exact Extract:

Pega’s asynchronous processing capabilities, as outlined in Pega Academy’sLead System Architect Missionand thePega Certified Lead System Architect Study Guide, provide mechanisms like queue processors, agents, and job schedulers for handling background tasks. For sending email notifications without impacting application performance, queue processors are the preferred choice due to their scalability and efficiency.

Option A (Incorrect): Standard agents are legacy components that process tasks in batches, which can introduce delays and are less scalable than queue processors. They are not recommended for real-time tasks like notifications, per theAsynchronous Processingmodule.

Option B (Correct): A standard queue processor is ideal for sending email notifications asynchronously. It processes tasks in a scalable, event-driven manner, ensuring that the email-sending process does not block the main application, thus maintaining responsiveness. This aligns with Pega’s best practices for background processing, as documented in theQueue Processor Configurationsection of Pega Community.

Option C (Incorrect): Advanced agents, like standard agents, are legacy and less efficient for high-volume, real-time tasks. Pega discourages their use in modern applications, favoring queue processors, per theAgent Processingguidelines.

Option D (Incorrect): Job schedulers are designed for recurring, time-based tasks (e.g., daily reports), not for event-driven tasks like sending notifications based on user actions. They are unsuitable for this requirement, as noted in theJob Scheduler Configurationmodule.