Question 130Two Panorama management nodes operate independently without an agreed HA failover process, risking contradictory device-group pushes. Which direct security or availability risk is most likely if this is not corrected? High-delay collector interconnections can destabilize ingestion under ordinary network failures. Independent managers can push conflicting rules during a control-plane failure. Single-collector dependency can erase visibility during the most important failure interval. Unplanned log duplication may force premature log deletion or backpressure on security telemetry. ExplanationCorrect Answer B:Independent managers can push conflicting rules during a control-plane failure. The underlying condition is: Two Panorama management nodes operate independently without an agreed HA failover process, risking contradictory device-group pushes. Prevent this consequence through: Design a compatible Panorama HA pair with validated configuration synchronization and controlled failure testing. Confirm with: A simulated primary outage transfers management responsibility without deploying divergent security policy. Incorrect Answers A:Resilience design must respect product cluster communication constraints as well as physical distribution. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Independent managers can push conflicting rules during a control-plane failure. C:Logging resilience depends on redundancy and collector quorum, not only spare disk space on one appliance. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Independent managers can push conflicting rules during a control-plane failure. D:Log redundancy changes capacity needs and can lower effective ingestion headroom for a fixed collector fleet. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Independent managers can push conflicting rules during a control-plane failure.
Question 131An AI review committee evaluates prompt-injection risk but ignores training-data poisoning and malicious retrieval sources. Following this design choice — Expand the AI threat model to distinguish model, retrieval, prompt and agent lifecycle risks. — which result most directly verifies the intended outcome? The intended assistant is allowed but a similarly named unapproved service remains blocked. A seeded card-number pattern is denied and the architecture review records permitted non-card alternatives. The assessment maps concrete controls and ownership to both poisoned retrieval and malicious user prompts. A higher-risk tool-capable agent receives stronger policy and requires documented owner approval. ExplanationCorrect Answer C:The assessment maps concrete controls and ownership to both poisoned retrieval and malicious user prompts. That observation confirms the intended action: Expand the AI threat model to distinguish model, retrieval, prompt and agent lifecycle risks. It addresses the immediate exposure: Unaddressed data-source attacks can manipulate model decisions even when prompt filtering works. Incorrect Answers A:AI app classification must resolve the concrete service identity rather than trust ambiguous display names. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The assessment maps concrete controls and ownership to both poisoned retrieval and malicious user prompts. B:Transport encryption does not substitute for scope reduction and policy controls on regulated cardholder data. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The assessment maps concrete controls and ownership to both poisoned retrieval and malicious user prompts. D:The same model interface may carry radically different risks when connected to privileged tools. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The assessment maps concrete controls and ownership to both poisoned retrieval and malicious user prompts.
Question 132Branch SD-WAN segmentation needs user-specific access decisions but the design has only per-circuit address objects. What is the most appropriate Palo Alto Networks architecture or security-control response for this situation? Design CIE-backed identity integration for Prisma Access users and validate revocation behavior. Use a supported on-premises directory synchronization agent with outbound connectivity and scoped privileges. Integrate the supported CIE identity and group data into NGFW policy with a defined sync health check. Evaluate compatible Cloud Identity Engine and Prisma SD-WAN identity policy capabilities for the intended role controls. ExplanationCorrect Answer D:Evaluate compatible Cloud Identity Engine and Prisma SD-WAN identity policy capabilities for the intended role controls. The controlling fact is: Branch SD-WAN segmentation needs user-specific access decisions but the design has only per-circuit address objects. The relevant reason is: Branch identity enforcement must link access to users or devices rather than assume all circuit traffic is equivalent. Verify by checking: An authorized branch test identity reaches its application and a different role is denied despite using the same circuit. Incorrect Answers A:Remote access control should consume authoritative identity lifecycle changes rather than disconnected local records. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate compatible Cloud Identity Engine and Prisma SD-WAN identity policy capabilities for the intended role controls. The governing reason is: Branch identity enforcement must link access to users or devices rather than assume all circuit traffic is equivalent. B:Directory synchronization architecture must align to where authoritative identities reside and how they are reachable. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate compatible Cloud Identity Engine and Prisma SD-WAN identity policy capabilities for the intended role controls. The governing reason is: Branch identity enforcement must link access to users or devices rather than assume all circuit traffic is equivalent. C:Central directory group synchronization can improve NGFW access accuracy when mappings remain current. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate compatible Cloud Identity Engine and Prisma SD-WAN identity policy capabilities for the intended role controls. The governing reason is: Branch identity enforcement must link access to users or devices rather than assume all circuit traffic is equivalent.
Question 133A marketing team wants to sanction one AI-writing app while denying its unapproved document-upload feature. Which direct security or availability risk is most likely if this is not corrected? An entire sanctioned app can become a covert bulk-upload channel if activities are not differentiated. Unreviewed patient data in external prompts can create regulatory and patient trust exposure. Excess prompt retention can create avoidable privacy and discovery liabilities. Broad matching can approve a lookalike AI destination and expose corporate content. ExplanationCorrect Answer A:An entire sanctioned app can become a covert bulk-upload channel if activities are not differentiated. The underlying condition is: A marketing team wants to sanction one AI-writing app while denying its unapproved document-upload feature. Prevent this consequence through: Classify the AI service and enforce the specific approved user activities with a compatible policy. Confirm with: The writing task succeeds but a confidential document upload is blocked for the same user. Incorrect Answers B:Compliance frameworks require demonstrable data handling controls, not an assumption that vendor branding implies compliance. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An entire sanctioned app can become a covert bulk-upload channel if activities are not differentiated. C:Security observability must be balanced with purpose limitation and lawful retention of personal data. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An entire sanctioned app can become a covert bulk-upload channel if activities are not differentiated. D:AI app classification must resolve the concrete service identity rather than trust ambiguous display names. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An entire sanctioned app can become a covert bulk-upload channel if activities are not differentiated.
Question 134A bank puts all AI model-scanning duties on its real-time prompt inspection service, then releases unchecked artifacts. What is the most appropriate Palo Alto Networks architecture or security-control response for this situation? Evaluate a supported API-intercept integration rather than mandating a network appliance outside the team's traffic path. Separate predeployment model assessment from real-time traffic inspection in the AI security reference architecture. Validate streaming protocol and session behavior against the selected AI security product's supported inspection mode. Include agent-to-tool calls and service identities in the applicable AI runtime and authorization architecture. ExplanationCorrect Answer B:Separate predeployment model assessment from real-time traffic inspection in the AI security reference architecture. The controlling fact is: A bank puts all AI model-scanning duties on its real-time prompt inspection service, then releases unchecked artifacts. The relevant reason is: Different AI attack surfaces require distinct complementary lifecycle controls rather than one universal scan. Verify by checking: The deployment gate reports artifact findings and the runtime gate separately records prompt attack verdicts. Incorrect Answers A:AI runtime form factor selection depends on whether the app exposes programmable calls or interceptable network flows. That is relevant to a different intervention. For the stated situation, the required action is: Separate predeployment model assessment from real-time traffic inspection in the AI security reference architecture. The governing reason is: Different AI attack surfaces require distinct complementary lifecycle controls rather than one universal scan. C:An architectural reference design must fit application protocols and throughput requirements, not only basic API examples. That is relevant to a different intervention. For the stated situation, the required action is: Separate predeployment model assessment from real-time traffic inspection in the AI security reference architecture. The governing reason is: Different AI attack surfaces require distinct complementary lifecycle controls rather than one universal scan. D:Agentic security must account for machine-generated actions, not solely user-entered prompts. That is relevant to a different intervention. For the stated situation, the required action is: Separate predeployment model assessment from real-time traffic inspection in the AI security reference architecture. The governing reason is: Different AI attack surfaces require distinct complementary lifecycle controls rather than one universal scan.
Question 135A contractor leaves the engagement but a browser access grant remains while the parent private connector continues serving other customers. What is the most appropriate Palo Alto Networks architecture or security-control response for this situation? Evaluate Prisma Browser private application access with supported Connector integration and scoped identity controls. Validate supported private application target types for the browser connector before deploying. Revoke the individual Prisma Browser app entitlement without indiscriminately disabling the shared connector. Bind Prisma Browser private app entitlements to trusted authentication profiles and explicit directory groups. ExplanationCorrect Answer C:Revoke the individual Prisma Browser app entitlement without indiscriminately disabling the shared connector. The controlling fact is: A contractor leaves the engagement but a browser access grant remains while the parent private connector continues serving other customers. The relevant reason is: Entitlement removal should target the departing user rather than disrupt shared private connectivity. Verify by checking: The former contractor cannot open the app while other authorized users retain normal browser access. Incorrect Answers A:Browser-mediated application access can reduce device-wide network trust for unmanaged endpoints. That is relevant to a different intervention. For the stated situation, the required action is: Revoke the individual Prisma Browser app entitlement without indiscriminately disabling the shared connector. The governing reason is: Entitlement removal should target the departing user rather than disrupt shared private connectivity. B:Different private-app client form factors do not necessarily support identical target representations. That is relevant to a different intervention. For the stated situation, the required action is: Revoke the individual Prisma Browser app entitlement without indiscriminately disabling the shared connector. The governing reason is: Entitlement removal should target the departing user rather than disrupt shared private connectivity. D:Browser security controls should authenticate named users and authorize particular applications independently. That is relevant to a different intervention. For the stated situation, the required action is: Revoke the individual Prisma Browser app entitlement without indiscriminately disabling the shared connector. The governing reason is: Entitlement removal should target the departing user rather than disrupt shared private connectivity.
Question 136A device changes manufacturer fingerprint after a firmware replacement, but policy grants access based only on its original type. The proposed architectural response is: Validate Device-ID profile changes and define safe handling for unidentified or mismatched equipment. Which technical or security architecture principle best supports this response? Device identity can inform policy where addresses are dynamically allocated across unlike device types. Vendor identity is a useful attribute but not sufficient proof of each device's business entitlement. Device-aware policy value depends on rule precedence and session matching at the real enforcement point. Device identification must be continuously verified and not treated as permanently immutable. ExplanationCorrect Answer D:Device identification must be continuously verified and not treated as permanently immutable. This principle is directly relevant to the proposed correction: Validate Device-ID profile changes and define safe handling for unidentified or mismatched equipment. A successful controlled test should show: A test mismatch triggers the expected restricted state until the device is positively reclassified. Incorrect Answers A:Device identity can inform policy where addresses are dynamically allocated across unlike device types. This does not establish the proposed intervention. The governing principle here is: Device identification must be continuously verified and not treated as permanently immutable. Apply it by: Validate Device-ID profile changes and define safe handling for unidentified or mismatched equipment. B:Vendor identity is a useful attribute but not sufficient proof of each device's business entitlement. This does not establish the proposed intervention. The governing principle here is: Device identification must be continuously verified and not treated as permanently immutable. Apply it by: Validate Device-ID profile changes and define safe handling for unidentified or mismatched equipment. C:Device-aware policy value depends on rule precedence and session matching at the real enforcement point. This does not establish the proposed intervention. The governing principle here is: Device identification must be continuously verified and not treated as permanently immutable. Apply it by: Validate Device-ID profile changes and define safe handling for unidentified or mismatched equipment.
Question 137A storage company estimates that increasing VM-Series vCPUs alone will double decryption performance on heavily oversubscribed hosts. Following this design choice — Model physical CPU headroom, NUMA placement, dataplane acceleration and cipher profile before capacity changes. — which result most directly verifies the intended outcome? An isolated workload benchmark identifies the real limiting resource and verifies the approved sizing fix. A controlled route event and peak load test keep approved core services within their recovery objectives. An unauthorized application-to-database flow across racks is denied without affecting approved service calls. Both a high-handshake test and a sustained-stream test meet security and latency thresholds. ExplanationCorrect Answer A:An isolated workload benchmark identifies the real limiting resource and verifies the approved sizing fix. That observation confirms the intended action: Model physical CPU headroom, NUMA placement, dataplane acceleration and cipher profile before capacity changes. It addresses the immediate exposure: Blind vCPU oversubscription can worsen latency while failing to add usable inspection capacity. Incorrect Answers B:Core security architecture must support sustained transit traffic and route convergence for critical networks. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An isolated workload benchmark identifies the real limiting resource and verifies the approved sizing fix. C: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: An isolated workload benchmark identifies the real limiting resource and verifies the approved sizing fix. D:Decryption capacity has multiple dimensions, including connection churn and cipher processing. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An isolated workload benchmark identifies the real limiting resource and verifies the approved sizing fix.
Question 138An Okta group rename causes inconsistent policies because the design relies on friendly text names that are reused. The proposed architectural response is: Confirm supported CIE group identifiers and synchronization mappings, then test group rename and deletion scenarios. Which technical or security architecture principle best supports this response? Log transport selection should fit event volume, delivery semantics and receiver capacity. Identity attributes used for policy must remain traceable to the intended authoritative directory object. Directory synchronization architecture must align to where authoritative identities reside and how they are reachable. Identity sync design should reduce unnecessary disclosure and follow least privilege without losing needed access signals. ExplanationCorrect Answer B:Identity attributes used for policy must remain traceable to the intended authoritative directory object. This principle is directly relevant to the proposed correction: Confirm supported CIE group identifiers and synchronization mappings, then test group rename and deletion scenarios. A successful controlled test should show: After the controlled rename, the correct group's entitlements remain intact and an unrelated group gains no access. Incorrect Answers A:Log transport selection should fit event volume, delivery semantics and receiver capacity. This does not establish the proposed intervention. The governing principle here is: Identity attributes used for policy must remain traceable to the intended authoritative directory object. Apply it by: Confirm supported CIE group identifiers and synchronization mappings, then test group rename and deletion scenarios. C:Directory synchronization architecture must align to where authoritative identities reside and how they are reachable. This does not establish the proposed intervention. The governing principle here is: Identity attributes used for policy must remain traceable to the intended authoritative directory object. Apply it by: Confirm supported CIE group identifiers and synchronization mappings, then test group rename and deletion scenarios. D:Identity sync design should reduce unnecessary disclosure and follow least privilege without losing needed access signals. This does not establish the proposed intervention. The governing principle here is: Identity attributes used for policy must remain traceable to the intended authoritative directory object. Apply it by: Confirm supported CIE group identifiers and synchronization mappings, then test group rename and deletion scenarios.
Question 139An IoT architecture correlates traffic from several locations without preserving site metadata from each collector. What is the most appropriate Palo Alto Networks architecture or security-control response for this situation? Plan a suitable discovery observation window and active-safe inventory reconciliation with network and asset records. Design inventory inference using supported metadata and protocol indicators without claiming encrypted content visibility. Preserve site, interface, zone and collector identity in the normalized device visibility pipeline. Map IoT visibility sources, including NGFW, virtual metadata collectors and supported SD-WAN sensors, by zone. ExplanationCorrect Answer C:Preserve site, interface, zone and collector identity in the normalized device visibility pipeline. The controlling fact is: An IoT architecture correlates traffic from several locations without preserving site metadata from each collector. The relevant reason is: Accurate device risk scoring requires the correct environmental context alongside observed protocol data. Verify by checking: The same model of sensor in two plants appears as distinct assets with the correct originating sites. Incorrect Answers A:Passive device discovery must account for low-frequency traffic and operational safety constraints. That is relevant to a different intervention. For the stated situation, the required action is: Preserve site, interface, zone and collector identity in the normalized device visibility pipeline. The governing reason is: Accurate device risk scoring requires the correct environmental context alongside observed protocol data. B:Device visibility may rely on traffic metadata when content cannot legally or technically be inspected. That is relevant to a different intervention. For the stated situation, the required action is: Preserve site, interface, zone and collector identity in the normalized device visibility pipeline. The governing reason is: Accurate device risk scoring requires the correct environmental context alongside observed protocol data. D:Device Security visibility cannot be assumed for network segments that provide no usable telemetry. That is relevant to a different intervention. For the stated situation, the required action is: Preserve site, interface, zone and collector identity in the normalized device visibility pipeline. The governing reason is: Accurate device risk scoring requires the correct environmental context alongside observed protocol data.
Question 140A storage company estimates that increasing VM-Series vCPUs alone will double decryption performance on heavily oversubscribed hosts. What is the most appropriate Palo Alto Networks architecture or security-control response for this situation? Design targeted supported decryption exemptions based on verified application constraints and approved clinical risk review. Recalculate effective throughput with realistic TLS cipher suites, session rates and privacy exceptions. Size the SSL inspection tier using realistic handshakes, concurrent sessions and representative encrypted workloads. Model physical CPU headroom, NUMA placement, dataplane acceleration and cipher profile before capacity changes. ExplanationCorrect Answer D:Model physical CPU headroom, NUMA placement, dataplane acceleration and cipher profile before capacity changes. The controlling fact is: A storage company estimates that increasing VM-Series vCPUs alone will double decryption performance on heavily oversubscribed hosts. The relevant reason is: Virtual inspection scaling depends on underlying host resources and supported I/O configuration, not vCPU count alone. Verify by checking: An isolated workload benchmark identifies the real limiting resource and verifies the approved sizing fix. Incorrect Answers A:Certificate pinning and other TLS protections can make blanket interception incompatible with critical applications. That is relevant to a different intervention. For the stated situation, the required action is: Model physical CPU headroom, NUMA placement, dataplane acceleration and cipher profile before capacity changes. The governing reason is: Virtual inspection scaling depends on underlying host resources and supported I/O configuration, not vCPU count alone. B:Decryption consumes substantial dataplane resources and cannot be sized from unencrypted traffic benchmarks alone. That is relevant to a different intervention. For the stated situation, the required action is: Model physical CPU headroom, NUMA placement, dataplane acceleration and cipher profile before capacity changes. The governing reason is: Virtual inspection scaling depends on underlying host resources and supported I/O configuration, not vCPU count alone. C:Decryption capacity has multiple dimensions, including connection churn and cipher processing. That is relevant to a different intervention. For the stated situation, the required action is: Model physical CPU headroom, NUMA placement, dataplane acceleration and cipher profile before capacity changes. The governing reason is: Virtual inspection scaling depends on underlying host resources and supported I/O configuration, not vCPU count alone.