Palo Alto Networks NetSec-Architect Practice Test 21
Question 200
For an original educational Network Security Architect scenario, consider: A regulated chat service has a secondary inference region but runtime guardrails only protect the primary route, creating an uninspected disaster-recovery path. Select THREE compatible elements: a proper correction, a targeted diagnostic and an acceptance result.
- Result: Recovery stays within the agreed business availability and risk requirements, with no hidden bypass of critical inspection on failover.
- Result: Approved enterprise AI workflows remain usable and unsanctioned data transfers are logged or prevented per policy.
- Change: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion.
- Check: Exercise representative inspection failures and regional failover while checking request routes, policy decisions, latency and alerting.
- Change: Design redundant AI inspection paths with explicit fail-open versus fail-closed policy, capacity and observability for every primary and recovery route.
- Check: Verify the actual application integration path, inspection coverage, data classification tests, blocking outcome and telemetry on permitted and rejected prompts.
Explanation
Correct Answer
A:Availability and risk posture must be planned together; an uninspected backup path or silent fail-open can defeat otherwise correct AI security controls. Required intervention: Design redundant AI inspection paths with explicit fail-open versus fail-closed policy, capacity and observability for every primary and recovery route.
D:Availability and risk posture must be planned together; an uninspected backup path or silent fail-open can defeat otherwise correct AI security controls. Acceptance: Recovery stays within the agreed business availability and risk requirements, with no hidden bypass of critical inspection on failover.
E:Availability and risk posture must be planned together; an uninspected backup path or silent fail-open can defeat otherwise correct AI security controls. Evidence: Exercise representative inspection failures and regional failover while checking request routes, policy decisions, latency and alerting.
Incorrect Answers
B:Result: Approved enterprise AI workflows remain usable and unsanctioned data transfers are logged or prevented per policy. Availability and risk posture must be planned together; an uninspected backup path or silent fail-open can defeat otherwise correct AI security controls.
C:Change: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion. Availability and risk posture must be planned together; an uninspected backup path or silent fail-open can defeat otherwise correct AI security controls.
F:Check: Verify the actual application integration path, inspection coverage, data classification tests, blocking outcome and telemetry on permitted and rejected prompts. Availability and risk posture must be planned together; an uninspected backup path or silent fail-open can defeat otherwise correct AI security controls.
Question 201
A network security architect is reviewing this environment: A development team refreshes a foundation model weekly but never repeats security checks when an updated checkpoint changes behavior. A proposed shortcut is: Reuse the initial model approval permanently even when the agent gains new tools and unreviewed data access. What should the security architect recommend as the narrowly scoped correction? Select ONE best answer.
- Discover and classify AI application use, then apply role-aware sanctioned-app controls and documented data sharing restrictions.
- Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion.
- Reuse the initial model approval permanently even when the agent gains new tools and unreviewed data access.
- Map AI model and application data flows to applicable regulatory obligations and risk controls, then choose architecture and enforcement based on documented requirements.
Explanation
Correct Answer
B:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Incorrect Answers
A:Discover and classify AI application use, then apply role-aware sanctioned-app controls and documented data sharing restrictions. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
C:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
D:This option addresses a different security architecture topic (AI governance and regulated data mapping) rather than the documented AI model and application lifecycle change control decision.
Question 202
A Palo Alto Networks architecture review finds: A development team refreshes a foundation model weekly but never repeats security checks when an updated checkpoint changes behavior. A design team proposes: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion. Which architecture principle most strongly supports the recommended response? Select ONE best answer.
- AI application security decisions depend on application identity, tenant and data handling policy, not on whether a URL contains the word artificial intelligence.
- A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
- An allowed AI application does not imply all data is appropriate to submit; classification and policy must govern each disclosure channel.
- Adversarial evaluation probes model and application behavior under malicious prompts, while perimeter firewall tests alone do not expose unsafe agent reasoning or tool permissions.
Explanation
Correct Answer
B:Relevant validation before approval: Match change tickets to artifact hashes, release configurations, risk assessments, red-team results and actual runtime policy coverage. This principle explains the proposed architecture, which is: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion.
Incorrect Answers
A:AI application security decisions depend on application identity, tenant and data handling policy, not on whether a URL contains the word artificial intelligence. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
C:An allowed AI application does not imply all data is appropriate to submit; classification and policy must govern each disclosure channel. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
D:Adversarial evaluation probes model and application behavior under malicious prompts, while perimeter firewall tests alone do not expose unsafe agent reasoning or tool permissions. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Question 203
The architecture board has not yet authorized configuration changes. Current evidence indicates: A development team refreshes a foundation model weekly but never repeats security checks when an updated checkpoint changes behavior. Which evidence best tests the architecture diagnosis before approving a disruptive change? Select ONE best answer.
- Map namespace labels, pod service accounts, east-west flows, network policies and the selected enforcement integration under scale and rolling upgrades.
- Exercise representative inspection failures and regional failover while checking request routes, policy decisions, latency and alerting.
- Review discovered AI applications, associated users, sanctioned status, DLP event samples and enforcement rules for enterprise versus personal accounts.
- Match change tickets to artifact hashes, release configurations, risk assessments, red-team results and actual runtime policy coverage.
Explanation
Correct Answer
D:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Incorrect Answers
A:Map namespace labels, pod service accounts, east-west flows, network policies and the selected enforcement integration under scale and rolling upgrades. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
B:Exercise representative inspection failures and regional failover while checking request routes, policy decisions, latency and alerting. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
C:Review discovered AI applications, associated users, sanctioned status, DLP event samples and enforcement rules for enterprise versus personal accounts. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Question 204
The architecture team has implemented an approved correction and must now perform a production-safe acceptance test. Original problem: A development team refreshes a foundation model weekly but never repeats security checks when an updated checkpoint changes behavior. The operations owner requires positive and negative test evidence and confirmation that legitimate business workflows still function. Which acceptance result demonstrates improved security without breaking authorized workflows? Select ONE best answer.
- Risky action paths are blocked or constrained under approved test scenarios and the red-team findings are tracked to closure.
- Recovery stays within the agreed business availability and risk requirements, with no hidden bypass of critical inspection on failover.
- The targeted AI function is classified and handled according to business approval while unrelated authorized SaaS workflows continue.
- Every production AI release has corresponding documented assessment and controls; changed behavior is not silently approved by an older scan.
Explanation
Correct Answer
D:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions. The approved design step was: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion.
Incorrect Answers
A:Risky action paths are blocked or constrained under approved test scenarios and the red-team findings are tracked to closure. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
B:Recovery stays within the agreed business availability and risk requirements, with no hidden bypass of critical inspection on failover. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
C:The targeted AI function is classified and handled according to business approval while unrelated authorized SaaS workflows continue. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Question 205
A design sign-off request identifies the following problem: A development team refreshes a foundation model weekly but never repeats security checks when an updated checkpoint changes behavior. Which paired security change and validation should close the design review? Select ONE best answer.
- Change: Architect cluster-aware workload segmentation and suitable policy or runtime inspection for inference and agent components with narrowly defined communication paths. Verify: Map namespace labels, pod service accounts, east-west flows, network policies and the selected enforcement integration under scale and rolling upgrades.
- Change: Architect AI runtime protection at a supported enforcement point that can inspect prompts and responses for policy-defined risks before sensitive content is released. Verify: Verify the actual application integration path, inspection coverage, data classification tests, blocking outcome and telemetry on permitted and rejected prompts.
- Change: Design redundant AI inspection paths with explicit fail-open versus fail-closed policy, capacity and observability for every primary and recovery route. Verify: Exercise representative inspection failures and regional failover while checking request routes, policy decisions, latency and alerting.
- Change: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion. Verify: Match change tickets to artifact hashes, release configurations, risk assessments, red-team results and actual runtime policy coverage.
Explanation
Correct Answer
D:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions. The change is successful only when: Every production AI release has corresponding documented assessment and controls; changed behavior is not silently approved by an older scan.
Incorrect Answers
A:Change: Architect cluster-aware workload segmentation and suitable policy or runtime inspection for inference and agent components with narrowly defined communication paths. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
B:Change: Architect AI runtime protection at a supported enforcement point that can inspect prompts and responses for policy-defined risks before sensitive content is released. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
C:Change: Design redundant AI inspection paths with explicit fail-open versus fail-closed policy, capacity and observability for every primary and recovery route. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Question 206
A network security architect is reviewing this environment: A customer-facing chatbot adds a retrieval tool and a new external data source after its initial approval, but the original AI runtime policy no longer covers the new action. A proposed shortcut is: Reuse the initial model approval permanently even when the agent gains new tools and unreviewed data access. What should the security architect recommend as the narrowly scoped correction? Select ONE best answer.
- Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion.
- Select a Prisma AIRS deployment form factor and integration point consistent with who controls the model endpoint, network path and application API.
- Reuse the initial model approval permanently even when the agent gains new tools and unreviewed data access.
- Combine appropriate application identification and cloud-delivered classification features with granular AI application access policy and validation.
Explanation
Correct Answer
A:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Incorrect Answers
B:Select a Prisma AIRS deployment form factor and integration point consistent with who controls the model endpoint, network path and application API. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
C:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions. Use this instead: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion.
D:Combine appropriate application identification and cloud-delivered classification features with granular AI application access policy and validation. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Question 207
A Palo Alto Networks architecture review finds: A customer-facing chatbot adds a retrieval tool and a new external data source after its initial approval, but the original AI runtime policy no longer covers the new action. A design team proposes: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion. Which architecture principle most strongly supports the recommended response? Select ONE best answer.
- Model scanning assesses risks associated with a model artifact and its behavior before deployment; runtime inspection addresses a different exposure once the model is serving requests.
- AI inspection architectures vary between direct application/API integration and network or infrastructure enforcement; a valid design must observe the request/response path it claims to protect.
- A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
- AI-specific runtime threats can appear in model inputs, outputs and tool interactions; model scanning prior to release cannot inspect every later conversation.
Explanation
Correct Answer
C:Relevant validation before approval: Match change tickets to artifact hashes, release configurations, risk assessments, red-team results and actual runtime policy coverage.
Incorrect Answers
A:This option addresses a different security architecture topic (Prisma AIRS model scanning governance) rather than the documented AI model and application lifecycle change control decision.
B:AI inspection architectures vary between direct application/API integration and network or infrastructure enforcement; a valid design must observe the request/response path it claims to protect. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
D:AI-specific runtime threats can appear in model inputs, outputs and tool interactions; model scanning prior to release cannot inspect every later conversation. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Question 208
The architecture board has not yet authorized configuration changes. Current evidence indicates: A customer-facing chatbot adds a retrieval tool and a new external data source after its initial approval, but the original AI runtime policy no longer covers the new action. Which evidence best tests the architecture diagnosis before approving a disruptive change? Select ONE best answer.
- Exercise representative inspection failures and regional failover while checking request routes, policy decisions, latency and alerting.
- Match change tickets to artifact hashes, release configurations, risk assessments, red-team results and actual runtime policy coverage.
- Map namespace labels, pod service accounts, east-west flows, network policies and the selected enforcement integration under scale and rolling upgrades.
- Test synthetic sensitive records, matching classifiers, channel visibility, blocked requests, user notification and exception logging.
Explanation
Correct Answer
B:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Incorrect Answers
A:Exercise representative inspection failures and regional failover while checking request routes, policy decisions, latency and alerting. A customer-facing chatbot adds a retrieval tool and a new external data source after its initial approval, but the original AI runtime policy no longer covers the new action.
C:Map namespace labels, pod service accounts, east-west flows, network policies and the selected enforcement integration under scale and rolling upgrades. A customer-facing chatbot adds a retrieval tool and a new external data source after its initial approval, but the original AI runtime policy no longer covers the new action.
D:Test synthetic sensitive records, matching classifiers, channel visibility, blocked requests, user notification and exception logging. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Question 209
The architecture team has implemented an approved correction and must now perform a production-safe acceptance test. Original problem: A customer-facing chatbot adds a retrieval tool and a new external data source after its initial approval, but the original AI runtime policy no longer covers the new action. The operations owner requires positive and negative test evidence and confirmation that legitimate business workflows still function. Which acceptance result demonstrates improved security without breaking authorized workflows? Select ONE best answer.
- Untrusted text cannot cause unauthorized tool execution, and permitted tasks retain auditable identity and change approval.
- Every production AI release has corresponding documented assessment and controls; changed behavior is not silently approved by an older scan.
- Protected information is denied or masked according to classification while approved non-sensitive prompts complete normally.
- Approved enterprise AI workflows remain usable and unsanctioned data transfers are logged or prevented per policy.
Explanation
Correct Answer
B:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Incorrect Answers
A:Untrusted text cannot cause unauthorized tool execution, and permitted tasks retain auditable identity and change approval. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
C:Protected information is denied or masked according to classification while approved non-sensitive prompts complete normally. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
D:Approved enterprise AI workflows remain usable and unsanctioned data transfers are logged or prevented per policy. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
Question 210
For an original educational Network Security Architect scenario, consider: A customer-facing chatbot adds a retrieval tool and a new external data source after its initial approval, but the original AI runtime policy no longer covers the new action. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Discover and classify AI application use, then apply role-aware sanctioned-app controls and documented data sharing restrictions.
- Check: Exercise representative inspection failures and regional failover while checking request routes, policy decisions, latency and alerting.
- Check: Match change tickets to artifact hashes, release configurations, risk assessments, red-team results and actual runtime policy coverage.
- Reuse the initial model approval permanently even when the agent gains new tools and unreviewed data access.
- Change: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion.
Explanation
Correct Answer
C:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions. Required intervention: Define gated model, prompt, tool and application changes with appropriate model scanning, adversarial retesting and updated runtime enforcement before promotion.
E:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions. Evidence: Match change tickets to artifact hashes, release configurations, risk assessments, red-team results and actual runtime policy coverage.
Incorrect Answers
A:Change: Discover and classify AI application use, then apply role-aware sanctioned-app controls and documented data sharing restrictions. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
B:Check: Exercise representative inspection failures and regional failover while checking request routes, policy decisions, latency and alerting. A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.
D:A security evaluation is version-specific; introducing new model weights, tools or data integrations can invalidate previous assurance assumptions.