Prisma Access provides a dedicated, centralized notification profile framework specifically for surfacing operational incidents such as tunnel instability, and it is this framework - not a tunnel-specific checkbox or a dashboard-level email setting - that the engineer needs to configure. A notification profile lets an administrator define the conditions that should trigger an alert (including IPSec tunnel down or flapping conditions for Remote Networks), select the delivery method (email or webhook), and optionally scope the profile to specific subtenants, giving the engineer exactly the proactive, condition-based alerting needed to catch intermittent instability rather than only discovering it after users report symptoms. This makes option A the correct and only fully supported mechanism among the four choices. There is no " tunnel log notification rule " object as a distinct configuration construct in Prisma Access (option B); alerting is generated through notification profiles, not through a rule attached directly to log entries. The operational or SASE health dashboard (option C) provides a visual, near-real-time operational view of tunnel and infrastructure status, but it is a monitoring surface an administrator has to actively check, not an automated email-alerting configuration point in itself - dashboards do not natively " send " alerts without being paired with a notification profile. Option D describes a checkbox that does not exist as part of standard remote network IPSec tunnel configuration; monitoring and alerting is configured separately through Incidents and Alerts, not inline during tunnel setup.
Reference:Prisma Access - Incidents and Alerts, Notification Profiles.