ACC visibility is entirely dependent on logs actually reaching Strata Logging Service in the first place, and log generation in Prisma Access is not automatic for every policy by default - it requires that a log forwarding profile be explicitly attached to each Security policy rule, directing the relevant log types to Strata Logging Service. If any remote network policies are missing this attachment, whether due to an oversight during rule creation or a rule cloned from a template that lacked the profile, traffic matching those rules simply never generates the logs ACC depends on, producing exactly the gap in visibility described in the scenario. Systematically auditing and ensuring every Prisma Access policy has an appropriate log forwarding profile pointed at Strata Logging Service is therefore the correct, root-cause remediation, making option D correct. Reconfiguring remote networks to log directly to Panorama instead (option A) moves away from the documented, scalable Prisma Access logging architecture, in which Strata Logging Service is the authoritative log repository that ACC and other analytics surfaces query - this is a regression, not a fix. Option B describes a log aggregation setting that does not correct missing logs caused by absent forwarding profiles; Panorama does not independently aggregate logs from RN-SPNs outside of the Strata Logging Service pipeline. Option C ' s setting relates to whether historical data feeds predefined report templates, not to whether logs are being generated and forwarded from policy in the first place, so it does not address a genuine data gap.
Reference:Prisma Access - Log Forwarding Profiles and Strata Logging Service Integration with ACC.

IKE and IPSec negotiation events - including successful and failed Phase 1 (IKE SA) and Phase 2 (IPSec SA) exchanges, proposal mismatches, and negotiation timeouts - are recorded by PAN-OS as System log entries, not as part of the Traffic, Tunnel, or Decrypt log facilities, which each capture a different category of information. Because Phase 1 has already completed successfully in this scenario but Phase 2 negotiation appears to be failing or stalling, the actual diagnostic detail explaining why - such as a proxy-ID/traffic- selector mismatch, an unsupported Phase 2 encryption or authentication algorithm, or a PFS group mismatch between the CPE and Prisma Access - will be recorded as a specific IKE/IPSec negotiation message in System logs, making option B the correct log facility to review. Decrypt logs (option A) capture SSL/TLS decryption events for inspected web traffic and have no relevance to IPSec tunnel negotiation, which is a separate control-plane process entirely. Traffic logs (option C) record session-level information for traffic that has already been successfully permitted through a completed policy match; since the tunnel ' s data plane is not yet fully established, there is no session traffic to log in the first place. Tunnel logs (option D) generally reflect the operational status and utilization of an already-established tunnel, not the underlying IKE/IPSec negotiation failure detail needed to diagnose why Phase 2 never completed.
Reference:PAN-OS/Strata Logging Service - System Logs for IKE Phase 1/Phase 2 Negotiation Troubleshooting.

Palo Alto Networks AI Access Security integrates with Enterprise Data Loss Prevention (DLP) capabilities to control sensitive data within AI applications like ChatGPT. The most effective way to prevent users from uploading financial information is to:
* Define an Enterprise DLP rule:This rule would be configured to identify content that matches patterns or keywords associated with financial information (e.g., credit card numbers, bank account details, tax identifiers, financial statements).
* Apply the DLP rule to the AI Access Security policy:This policy would be specifically configured to inspect traffic to and from ChatGPT. When the DLP rule detects a user attempting to upload content containing financial information, it can take a defined action, such as blocking the upload.
Let's analyze why the other options are incorrect based on official documentation:
* A. Apply File Blocking to stop file uploads containing financial information.While File Blocking can prevent the upload of certain file types, it is not content-aware. It cannot inspect thecontentof a file to determine if it contains financial information. Therefore, it's not a granular or effective solution for this specific requirement.
* C. Add the ChatGPT domains using URL Filtering to block uploads containing financial information.URL Filtering controls access to specific websites or categories of websites. While you could potentially block access to ChatGPT entirely, it does not provide the capability to inspect the content being uploaded to a permitted domain and prevent the transfer of sensitive financial data.
* D. Apply a vulnerability profile to stop attempts to exploit system flaws or gain unauthorized access to financial systems.Vulnerability profiles are designed to detect and prevent attempts to exploit known security vulnerabilities in systems. They are not designed to inspect the content of user uploads for sensitive data like financial information. While importantfor overall security, they do not directly address the requirement of preventing financial data uploads to ChatGPT.
Therefore, configuring an Enterprise DLP rule within AI Access Security is the correct and most effective method to prevent users from uploading financial information to ChatGPT by inspecting the content of the uploads.

Preventing sensitive content specifically - such as financial information - from being uploaded to a generative AI application requires content-aware inspection capable of recognizing patterns like account numbers, financial statement data, or other regulated data types within the actual payload of the upload, which is precisely the function Enterprise DLP is designed to perform. AI Access Security integrates with Enterprise DLP so that an administrator can build a rule targeting the data patterns that constitute " financial information,
" and apply it specifically to traffic destined for sanctioned or monitored generative AI applications like ChatGPT, blocking the upload at the content level regardless of the file format or transport mechanism used.
This makes Enterprise DLP the correct complementary control to a Security policy, and option B the correct answer. File Blocking (option A) operates on file type and extension, not on the semantic content of a file or a text-based upload - it cannot selectively identify " financial information " within an otherwise permitted file type, so it is not a content-aware control suited to this requirement. URL Filtering (option C) governs access to categorized websites and can restrict or allow entire domains, but it has no capability to inspect the content of an upload for sensitive data patterns; it is a destination-control mechanism, not a data-loss-prevention mechanism. A vulnerability profile (option D) is designed to detect exploitation attempts against known software vulnerabilities, which is entirely unrelated to inspecting outbound user-submitted content for sensitive data.
Reference:AI Access Security - Enterprise DLP Integration for Generative AI Data Protection.