Question 760Prisma Access private service routes are built without accounting for reply paths through the secondary data center. Following this design choice — Map request and return routes through the protected off-ramps and verify stateful path symmetry. — which result most directly verifies the intended outcome? After a controlled loss of one path, authorized users reach the private app through the approved alternate. Users reach the correct same-address application in each subsidiary with distinct policy and log attribution. A roaming test user changes regions and retains only the original authorized API actions. Packet traces show requests and responses traverse the expected security services in normal and failure scenarios. ExplanationCorrect Answer D:Packet traces show requests and responses traverse the expected security services in normal and failure scenarios. That observation confirms the intended action: Map request and return routes through the protected off-ramps and verify stateful path symmetry. It addresses the immediate exposure: Asymmetric return flows can reset sessions or bypass intended private access inspection. Incorrect Answers A:Private app resilience requires independent reachable off-ramps when a data center or tunnel fails. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Packet traces show requests and responses traverse the expected security services in normal and failure scenarios. B:Overlapping private address domains require deliberate application identity and connector routing design. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Packet traces show requests and responses traverse the expected security services in normal and failure scenarios. C:Application authorization must remain consistent even when clients attach to different Prisma Access gateways. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Packet traces show requests and responses traverse the expected security services in normal and failure scenarios.
Question 761Two workloads on the same virtual subnet require separation although their IP addresses change during autoscaling. Which direct security or availability risk is most likely if this is not corrected? Broad same-subnet trust enables lateral movement when a workload is compromised. An uninspected intercompany shortcut can undermine the intended isolation of acquired systems. Unobserved policy regressions can interrupt vital business flows without timely diagnosis. Bidirectional broad trust permits enterprise malware to reach industrial operations. ExplanationCorrect Answer A:Broad same-subnet trust enables lateral movement when a workload is compromised. The underlying condition is: Two workloads on the same virtual subnet require separation although their IP addresses change during autoscaling. Prevent this consequence through: Introduce workload-aware microsegmentation tied to stable identity or application context at the east-west enforcement point. Confirm with: An unapproved pod-to-database connection is blocked after rescheduling without relying on a fixed source address. Incorrect Answers B:Security boundaries must exist on actual forwarding paths rather than only on a topology diagram. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Broad same-subnet trust enables lateral movement when a workload is compromised. C:Availability monitoring cannot establish that application-level authorization is correct across changing workloads. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Broad same-subnet trust enables lateral movement when a workload is compromised. D:Different operational functions should use distinct least-privilege segmentation rules with clear directionality. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Broad same-subnet trust enables lateral movement when a workload is compromised.
Question 762Security leadership sees a monthly firewall rule report but cannot tell whether Zero Trust policies remain enforced after changes. Following this design choice — Define continuous telemetry for policy hits, identity coverage, postures, threats and exceptions with measurable thresholds. — which result most directly verifies the intended outcome? Traffic logs show the approved Git transaction succeeds and unrelated services on the same server remain denied. Dashboards flag an intentional identity-coverage regression and link the alert to affected access decisions. Approved telemetry reaches collectors while unsolicited management sessions are denied and recorded. A simulated blocked critical dependency appears in the analytics and triggers the intended investigation workflow. ExplanationCorrect Answer B:Dashboards flag an intentional identity-coverage regression and link the alert to affected access decisions. That observation confirms the intended action: Define continuous telemetry for policy hits, identity coverage, postures, threats and exceptions with measurable thresholds. It addresses the immediate exposure: Undetected policy drift can erode least-privilege controls over successive releases. Incorrect Answers A:Application identity is a more precise authorization boundary than a shared server IP or open port. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Dashboards flag an intentional identity-coverage regression and link the alert to affected access decisions. C:Different operational functions should use distinct least-privilege segmentation rules with clear directionality. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Dashboards flag an intentional identity-coverage regression and link the alert to affected access decisions. D:Availability monitoring cannot establish that application-level authorization is correct across changing workloads. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Dashboards flag an intentional identity-coverage regression and link the alert to affected access decisions.
Question 763A contractor connects from an unmanaged endpoint and a source-IP-only security rule permits access to confidential payroll APIs. Which direct security or availability risk is most likely if this is not corrected? Ignoring deteriorating device posture can keep privileged access open during endpoint compromise. Stale user mappings can permit cross-role access to protected patient records. Trusting a borrowed address can expose sensitive payroll functions to an unverified endpoint. Permitted but uninspected sessions can carry exploit payloads into internal applications. ExplanationCorrect Answer C:Trusting a borrowed address can expose sensitive payroll functions to an unverified endpoint. The underlying condition is: A contractor connects from an unmanaged endpoint and a source-IP-only security rule permits access to confidential payroll APIs. Prevent this consequence through: Design a least-privilege rule requiring authenticated identity and validated HIP posture for the specific payroll application. Confirm with: A noncompliant test laptop is denied payroll access while the approved managed laptop is allowed and logged. Incorrect Answers A:An identity certificate alone does not demonstrate that an endpoint remains healthy enough for sensitive sessions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Trusting a borrowed address can expose sensitive payroll functions to an unverified endpoint. B:Dynamic User-ID bindings support differentiated access on shared network segments when identities change. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Trusting a borrowed address can expose sensitive payroll functions to an unverified endpoint. D:Allowing a connection does not make its payload or destination trustworthy over the rest of its session. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Trusting a borrowed address can expose sensitive payroll functions to an unverified endpoint.
Question 764Unmanaged partner laptops need one internal web application, but policy demands installation of a full device-wide VPN client. The proposed architectural response is: Evaluate Prisma Browser private application access with supported Connector integration and scoped identity controls. Which technical or security architecture principle best supports this response? Browser security controls should authenticate named users and authorize particular applications independently. Entitlement removal should target the departing user rather than disrupt shared private connectivity. Different private-app client form factors do not necessarily support identical target representations. Browser-mediated application access can reduce device-wide network trust for unmanaged endpoints. ExplanationCorrect Answer D:Browser-mediated application access can reduce device-wide network trust for unmanaged endpoints. This principle is directly relevant to the proposed correction: Evaluate Prisma Browser private application access with supported Connector integration and scoped identity controls. A successful controlled test should show: The approved partner browser opens only the required internal web app without exposing broad private subnet routes. Incorrect Answers A:Browser security controls should authenticate named users and authorize particular applications independently. This does not establish the proposed intervention. The governing principle here is: Browser-mediated application access can reduce device-wide network trust for unmanaged endpoints. Apply it by: Evaluate Prisma Browser private application access with supported Connector integration and scoped identity controls. B:Entitlement removal should target the departing user rather than disrupt shared private connectivity. This does not establish the proposed intervention. The governing principle here is: Browser-mediated application access can reduce device-wide network trust for unmanaged endpoints. Apply it by: Evaluate Prisma Browser private application access with supported Connector integration and scoped identity controls. C:Different private-app client form factors do not necessarily support identical target representations. This does not establish the proposed intervention. The governing principle here is: Browser-mediated application access can reduce device-wide network trust for unmanaged endpoints. Apply it by: Evaluate Prisma Browser private application access with supported Connector integration and scoped identity controls.
Question 765Staff use an unsanctioned application for chat, and policy currently blocks all SaaS communication, including approved tools. Which direct security or availability risk is most likely if this is not corrected? Indiscriminate blocks can drive users toward uncontrolled devices and private accounts. Blanket SaaS allowlisting can expose customer data through overpowered application features. Text-only scanning can allow photographed records to exit through permitted file uploads. Guest accounts with unrestricted SaaS sharing can leak sensitive internal documents. ExplanationCorrect Answer A:Indiscriminate blocks can drive users toward uncontrolled devices and private accounts. The underlying condition is: Staff use an unsanctioned application for chat, and policy currently blocks all SaaS communication, including approved tools. Prevent this consequence through: Classify application risk and enforce a granular sanctioning policy that preserves named approved services. Confirm with: The unknown chat app is blocked while the enterprise-approved collaboration app remains functional. Incorrect Answers B:Application authorization should distinguish legitimate activity from exfiltration within the same SaaS tool. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Indiscriminate blocks can drive users toward uncontrolled devices and private accounts. C:Sensitive information may reside in images and must not be treated as absent when plain text extraction is empty. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Indiscriminate blocks can drive users toward uncontrolled devices and private accounts. D:External user entitlements must be narrower than internal staff when business need differs. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Indiscriminate blocks can drive users toward uncontrolled devices and private accounts.
Question 766A remote factory has no NGFW on the local path, yet its IoT monitoring plan assumes firewall telemetry exists at every site. Following this design choice — Evaluate a supported virtual metadata collector or alternative sensor placement at the actual site. — which result most directly verifies the intended outcome? A planted test sensor on the previously dark plant subnet is identified with its actual source data. The selected collector reports representative factory device traffic without relying on a nonexistent local NGFW. A test branch device appears in the central inventory with correctly identified site and protocol behavior. The discovery pilot observes seeded sensor-to-controller and sensor-to-cloud sessions with proper attribution. ExplanationCorrect Answer B:The selected collector reports representative factory device traffic without relying on a nonexistent local NGFW. That observation confirms the intended action: Evaluate a supported virtual metadata collector or alternative sensor placement at the actual site. It addresses the immediate exposure: Architectures that assume absent sensors create false confidence in remote asset coverage. Incorrect Answers A:Device Security visibility cannot be assumed for network segments that provide no usable telemetry. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The selected collector reports representative factory device traffic without relying on a nonexistent local NGFW. C:Different WAN and firewall sensors can complement one another across distributed IoT networks. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The selected collector reports representative factory device traffic without relying on a nonexistent local NGFW. D:Sensor placement must cover actual packet paths, including internal device-to-device communication. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The selected collector reports representative factory device traffic without relying on a nonexistent local NGFW.
Question 767A private app appears in a ZTNA Connector target list but is missing from the Prisma Browser application catalog. Which direct security or availability risk is most likely if this is not corrected? Domain-based trust may grant private app access to unrelated external users. Broad connector shutdown can create a collateral outage during routine offboarding. A technically healthy connector can remain unusable when the application is not exposed correctly. Granting full tunnel access to unmanaged devices can unnecessarily expose other internal applications. ExplanationCorrect Answer C:A technically healthy connector can remain unusable when the application is not exposed correctly. The underlying condition is: A private app appears in a ZTNA Connector target list but is missing from the Prisma Browser application catalog. Prevent this consequence through: Create the corresponding allowed browser application definition with matching approved target and user groups. Confirm with: An entitled browser session opens the registered private app and a nonentitled account is rejected. Incorrect Answers A:Browser security controls should authenticate named users and authorize particular applications independently. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A technically healthy connector can remain unusable when the application is not exposed correctly. B:Entitlement removal should target the departing user rather than disrupt shared private connectivity. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A technically healthy connector can remain unusable when the application is not exposed correctly. D:Browser-mediated application access can reduce device-wide network trust for unmanaged endpoints. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A technically healthy connector can remain unusable when the application is not exposed correctly.
Question 768An HA firewall design enables ECMP for return paths but fails to account for a stateful session taking different members. Following this design choice — Verify ECMP hash, routing symmetry and state-sharing requirements before accepting the design. — which result most directly verifies the intended outcome? An unauthorized application-to-database flow across racks is denied without affecting approved service calls. Routing tests include the approved application prefixes and exclude seeded unrelated networks after convergence. An approved common policy change reaches all scoped firewalls and a local exception remains restricted. Packet traces demonstrate symmetric inspection for approved long-lived sessions across route events. ExplanationCorrect Answer D:Packet traces demonstrate symmetric inspection for approved long-lived sessions across route events. That observation confirms the intended action: Verify ECMP hash, routing symmetry and state-sharing requirements before accepting the design. It addresses the immediate exposure: Asymmetric paths can create intermittent application failures or unseen return traffic. Incorrect Answers A:Perimeter controls do not inspect traffic that remains inside a trusted compute fabric. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Packet traces demonstrate symmetric inspection for approved long-lived sessions across route events. B:Dynamic routing integration should propagate intentional reachability rather than every learned path by default. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Packet traces demonstrate symmetric inspection for approved long-lived sessions across route events. C:System management architecture should minimize configuration drift while preserving independent tenant rights. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Packet traces demonstrate symmetric inspection for approved long-lived sessions across route events.
Question 769A branch access design uses Colo-Connect for one region but leaves no documented dependency on its interconnect health. What is the most appropriate Palo Alto Networks architecture or security-control response for this situation? Model Colo-Connect or cloud NCC connectivity as a monitored and recoverable off-ramp dependency. Narrow target FQDN definitions and connector-group association, then validate resolution precedence. Evaluate ZTNA Connector application targets with distinct Connector IP Blocks for the overlapping networks. Constrain route advertisements and confirm intended prefix acceptance at the appropriate connection edges. ExplanationCorrect Answer A:Model Colo-Connect or cloud NCC connectivity as a monitored and recoverable off-ramp dependency. The controlling fact is: A branch access design uses Colo-Connect for one region but leaves no documented dependency on its interconnect health. The relevant reason is: Private interconnects are part of the application path and require resilience and fault isolation evidence. Verify by checking: A simulated interconnect failure surfaces in monitoring and the approved alternate is exercised successfully. Incorrect Answers B:Precise private application targeting is needed when multiple connectors could match the same name. That is relevant to a different intervention. For the stated situation, the required action is: Model Colo-Connect or cloud NCC connectivity as a monitored and recoverable off-ramp dependency. The governing reason is: Private interconnects are part of the application path and require resilience and fault isolation evidence. C:Connector-based private app access can decouple application identity from ambiguous underlying subnet addresses. That is relevant to a different intervention. For the stated situation, the required action is: Model Colo-Connect or cloud NCC connectivity as a monitored and recoverable off-ramp dependency. The governing reason is: Private interconnects are part of the application path and require resilience and fault isolation evidence. D:Routing between cloud SSE and private networks should expose only the required reachable address space. That is relevant to a different intervention. For the stated situation, the required action is: Model Colo-Connect or cloud NCC connectivity as a monitored and recoverable off-ramp dependency. The governing reason is: Private interconnects are part of the application path and require resilience and fault isolation evidence.
Question 770An internal AI agent can invoke file-deletion tools based on untrusted document text returned by retrieval. The proposed architectural response is: Threat-model agent tool permissions and apply AI runtime controls for prompt injection and risky tool calls. Which technical or security architecture principle best supports this response? Model artifact vetting provides a gate that is distinct from inspecting production user conversations. Agent authorization must not blindly promote retrieved untrusted text into executable authority. Adversarial model testing needs scoped authorization and environmental isolation independent of normal inference security. Protecting AI traffic also requires constraining lateral network reachability among containerized components. ExplanationCorrect Answer B:Agent authorization must not blindly promote retrieved untrusted text into executable authority. This principle is directly relevant to the proposed correction: Threat-model agent tool permissions and apply AI runtime controls for prompt injection and risky tool calls. A successful controlled test should show: A poisoned retrieved passage fails to trigger the destructive tool while an approved task continues under policy. Incorrect Answers A:Model artifact vetting provides a gate that is distinct from inspecting production user conversations. This does not establish the proposed intervention. The governing principle here is: Agent authorization must not blindly promote retrieved untrusted text into executable authority. Apply it by: Threat-model agent tool permissions and apply AI runtime controls for prompt injection and risky tool calls. C:Adversarial model testing needs scoped authorization and environmental isolation independent of normal inference security. This does not establish the proposed intervention. The governing principle here is: Agent authorization must not blindly promote retrieved untrusted text into executable authority. Apply it by: Threat-model agent tool permissions and apply AI runtime controls for prompt injection and risky tool calls. D:Protecting AI traffic also requires constraining lateral network reachability among containerized components. This does not establish the proposed intervention. The governing principle here is: Agent authorization must not blindly promote retrieved untrusted text into executable authority. Apply it by: Threat-model agent tool permissions and apply AI runtime controls for prompt injection and risky tool calls.