Pass Palo Alto Networks NetSec-Architect Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Palo Alto Networks NetSec-Architect Practice Test 56
Question 550
At fictional Eastfield Data Platforms, the design team must verify failure behavior and compliance without expanding unnecessary application exposure. Architecture risk: A data center refresh picks a firewall pair based only on edge internet throughput despite significant encrypted east-west traffic and growth. Evidence: Capacity model shows east-west peak sessions, decryption and application inspection load exceed the proposed platform reserve. Which narrowly scoped design action AND separately measurable postchange confirmation together form the most defensible response?
Explanation
Correct Answer
Capacity model shows east-west peak sessions, decryption and application inspection load exceed the proposed platform reserve. The paired correction is to select the appropriate PA-Series/VM-Series form factor and hardware generation using explicit edge, core and east-west inspection sizing. Validate its effect with: A representative peak workload and failover load test remain within CPU, session and latency guardrails. Private cloud firewall selection must account for inspection direction, hardware capabilities and growth reserve.
Incorrect Answers
At Eastfield Data Platforms, the offered action and verification—design role-scoped management, configuration versioning, audit logging, dedicated management network and change approval—do not establish closure of the stated failure. The case evidence is that capacity model shows east-west peak sessions, decryption and application inspection load exceed the proposed platform reserve. The relevant response is to select the appropriate PA-Series/VM-Series form factor and hardware generation using explicit edge, core and east-west inspection sizing. Check its effect against: A representative peak workload and failover load test remain within CPU, session and latency guardrails.
At Eastfield Data Platforms, this pair does not address the recorded clue: capacity model shows east-west peak sessions, decryption and application inspection load exceed the proposed platform reserve. The scoped correction is to select the appropriate PA-Series/VM-Series form factor and hardware generation using explicit edge, core and east-west inspection sizing. Confirm success using: A representative peak workload and failover load test remain within CPU, session and latency guardrails.
The offered action and verification—architect symmetric routing with supported BGP/OSPF redistribution, ECMP policy and coherent HA advertisement/failover behavior—do not establish closure of the stated failure. The case evidence is that capacity model shows east-west peak sessions, decryption and application inspection load exceed the proposed platform reserve. The relevant response is to select the appropriate PA-Series/VM-Series form factor and hardware generation using explicit edge, core and east-west inspection sizing. Check its effect against: A representative peak workload and failover load test remain within CPU, session and latency guardrails.
Question 551
At fictional Silverline Research Consortium, the architecture team is responsible for private cloud (pa-series, vm-series, hypervisors) design, continuity, policy and architecture governance and must preserve least privilege, auditable change and measurable business availability. Risk case: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Verified finding: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Which scoped architecture decision most directly addresses the documented control gap without unnecessarily changing other services?
Explanation
Correct Answer
The evidence is that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The appropriate change is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings, because hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation. After the change, A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
Incorrect Answers
An alternative operation—architect supported active/passive or active/active HA, state synchronization and route failover matching required UDP/TCP recovery outcomes—does not directly resolve the recorded failure. Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The appropriate intervention is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
The proposed change—architect symmetric routing with supported BGP/OSPF redistribution, ECMP policy and coherent HA advertisement/failover behavior—does not repair the condition documented in the case. The decisive evidence is that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The necessary change is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
One alternative is to select the appropriate PA-Series/VM-Series form factor and hardware generation using explicit edge, core and east-west inspection sizing, but this does not address the decisive finding: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Instead, the correction is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Check the result using: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
Question 552
For fictional Silverline Research Consortium, architects investigating private cloud (pa-series, vm-series, hypervisors) design, continuity, policy and architecture governance observe this risk: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Before making broad configuration or topology changes, which finding most directly isolates the failure mechanism?
Explanation
Correct Answer
The record shows that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation. The corresponding correction is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
Incorrect Answers
An alternative finding indicates that BGP next-hop and ECMP route telemetry show unequal convergence times across the inspected and bypass paths; this is not the controlling evidence in the report. Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The appropriate correction is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
A competing observation indicates that failover captures reveal unsupported or incomplete state/session synchronization and delayed path convergence for the selected active/active design, which points away from this case. The distinguishing evidence is: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. That is consistent with the mechanism: hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
An alternative finding indicates that SCM/Panorama and local logs show missing individual actor identity, incomplete configuration snapshots and unmonitored management API credentials; this is not the controlling evidence in the report. Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The appropriate correction is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
Question 553
At fictional Silverline Research Consortium, the security design for private cloud (pa-series, vm-series, hypervisors) design, continuity, policy and architecture governance faces: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Diagnostic evidence: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Proposed design change: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Which independent observation would demonstrate that the change met its intended outcome?
Explanation
Correct Answer
A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. This post-change check addresses the recorded finding: hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
Incorrect Answers
An alternative result would show that A synthetic node loss meets the application's measured session recovery objective while all security policy remains enforced; it measures a different outcome. To check this fault, verify: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. The earlier evidence was that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings.
An alternative check—A test policy change is attributable to one authorized admin, recoverable from signed backup and denied for an unapproved role—is not sufficient closure evidence for this fault. The relevant acceptance test is: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
A different check—A representative peak workload and failover load test remain within CPU, session and latency guardrails—would not demonstrate that this particular failure was corrected. Acceptance instead requires this result: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. This tests the condition shown by hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings.
Question 554
For the architecture board of fictional Silverline Research Consortium, a proposed change to private cloud (pa-series, vm-series, hypervisors) design, continuity, policy and architecture governance follows this problem: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Discriminating observation: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Which network security architecture principle best explains why the existing design is insufficient?
Explanation
Correct Answer
The governing principle is: Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation. The case specifically shows hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The corresponding change is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
Incorrect Answers
An alternative principle holds that SSL inspection imposes CPU and memory overhead that must be included in capacity and availability planning, but this is not the mechanism shown here. This case reports that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Its governing principle is that hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
The cited mechanism, private cloud firewall selection must account for inspection direction, hardware capabilities and growth reserve, does not account for the recorded clue. Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
That alternative rule—layer-3 resilience and stateful inspection share responsibility for session path selection—does not explain the deciding observation: hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation. That is the mechanism the corrective action must address.
Question 555
At fictional Silverline Research Consortium, the design team must preserve least privilege, auditable change and measurable business availability. Architecture risk: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Evidence: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Which narrowly scoped design action AND separately measurable postchange confirmation together form the most defensible response?
Explanation
Correct Answer
The proposed action is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Independent verification is: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. That pair addresses the actual recorded clue: hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings.
Incorrect Answers
This pair does not resolve the recorded clue: hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The scoped correction is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Confirm success using: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
The offered action and verification—recalculate firewall sizing using realistic TLS decryption, certificate policy, inspection subscription and failover capacity assumptions—do not establish closure of the stated failure. The case evidence is that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The relevant response is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Check its effect against: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
At Silverline Research Consortium, this pair does not address the recorded clue: hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The scoped correction is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Confirm success using: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
Question 556
At fictional Helix Distribution Enterprise, the architecture team is responsible for cross-region private cloud (pa-series, vm-series, hypervisors) design validation during staged modernization and must verify failure behavior and compliance without expanding unnecessary application exposure. Risk case: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Verified finding: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Which scoped architecture decision most directly addresses the documented control gap without unnecessarily changing other services?
Explanation
Correct Answer
Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation. The direct correction is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Verify the outcome with: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
Incorrect Answers
One alternative is to architect supported active/passive or active/active HA, state synchronization and route failover matching required UDP/TCP recovery outcomes, but this does not address the decisive finding: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Instead, the correction is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Check the result using: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
An alternative operation—select the appropriate PA-Series/VM-Series form factor and hardware generation using explicit edge, core and east-west inspection sizing—does not directly resolve the recorded failure. Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The appropriate intervention is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
At Helix Distribution Enterprise, the proposed change—architect symmetric routing with supported BGP/OSPF redistribution, ECMP policy and coherent HA advertisement/failover behavior—does not repair the condition documented in the case. The decisive evidence is that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The necessary change is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
Question 557
For fictional Helix Distribution Enterprise, architects investigating cross-region private cloud (pa-series, vm-series, hypervisors) design validation during staged modernization observe this risk: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Before making broad configuration or topology changes, which finding most directly isolates the failure mechanism?
Explanation
Correct Answer
The evidence shows that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation. The direct correction is: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
Incorrect Answers
At Helix Distribution Enterprise, the offered observation is that failover captures reveal unsupported or incomplete state/session synchronization and delayed path convergence for the selected active/active design, which points away from this case. The distinguishing evidence is: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. That is consistent with the mechanism: hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
A different observation—capacity model shows east-west peak sessions, decryption and application inspection load exceed the proposed platform reserve—does not establish the specific fault described here. The record instead shows this: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
A competing observation indicates that baseline and inspection tests reveal material throughput drop under the real TLS cipher and concurrent-session mix, which points away from this case. The distinguishing evidence is: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. That is consistent with the mechanism: hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
Question 558
At fictional Helix Distribution Enterprise, the security design for cross-region private cloud (pa-series, vm-series, hypervisors) design validation during staged modernization faces: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Diagnostic evidence: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Proposed design change: Design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Which independent observation would demonstrate that the change met its intended outcome?
Explanation
Correct Answer
Verify the result with: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. This tests the correction against the actual evidence: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
Incorrect Answers
At Helix Distribution Enterprise, the proposed check—A representative peak workload and failover load test remain within CPU, session and latency guardrails—would not demonstrate that this particular failure was corrected. Acceptance instead requires this result: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. This tests the condition shown by hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings.
An alternative result would show that after route flap, controlled TCP and UDP flows remain inspected and required connectivity recovers within objective; it measures a different outcome. To check this fault, verify: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. The earlier evidence was that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings.
At Helix Distribution Enterprise, the suggested check—A test policy change is attributable to one authorized admin, recoverable from signed backup and denied for an unapproved role—is not sufficient closure evidence for this fault. The relevant acceptance test is: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
Question 559
For the architecture board of fictional Helix Distribution Enterprise, a proposed change to cross-region private cloud (pa-series, vm-series, hypervisors) design validation during staged modernization follows this problem: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Discriminating observation: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Which network security architecture principle best explains why the existing design is insufficient?
Explanation
Correct Answer
Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation. That distinction fits the observed clue: hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The practical fix is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings.
Incorrect Answers
An alternative principle holds that high availability design must test real protocol/state behavior, not only whether a standby device reports green, but this is not the mechanism shown here. This case reports that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Its governing principle is that hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
The cited mechanism, architectural operational controls must protect management plane integrity as carefully as packet inspection, does not account for the recorded clue. Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
At Helix Distribution Enterprise, the offered rule—layer-3 resilience and stateful inspection share responsibility for session path selection—does not explain the deciding observation: hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation. That is the mechanism the corrective action must address.
Question 560
At fictional Helix Distribution Enterprise, the design team must verify failure behavior and compliance without expanding unnecessary application exposure. Architecture risk: A VM-Series security instance on ESXi/KVM is allocated high vCPU count yet encrypted traffic throughput is lower than a smaller tuned instance. Evidence: Hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. Which narrowly scoped design action AND separately measurable postchange confirmation together form the most defensible response?
Explanation
Correct Answer
The observation is that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The response is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. The separate acceptance check is: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention. Hypervisor locality and supported dataplane acceleration can matter more than headline vCPU allocation.
Incorrect Answers
That alternative would test a different outcome: select the appropriate PA-Series/VM-Series form factor and hardware generation using explicit edge, core and east-west inspection sizing. Independent proof: A representative peak workload and failover load test remain within CPU, session and latency guardrails. Here, hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The paired response is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Its acceptance check is: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
At Helix Distribution Enterprise, this pair does not address the recorded clue: hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The scoped correction is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Confirm success using: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
At Helix Distribution Enterprise, the offered action and verification—recalculate firewall sizing using realistic TLS decryption, certificate policy, inspection subscription and failover capacity assumptions—do not establish closure of the stated failure. The case evidence is that hypervisor metrics show vCPU scheduling across NUMA boundaries with unsupported offload/DPDK or SR-IOV settings. The relevant response is to design supported per-hypervisor VM-Series vCPU/NUMA placement, dedicated dataplane resources and hardware acceleration settings. Check its effect against: A controlled encrypted throughput test improves packet processing and remains stable under virtual-host contention.
Palo Alto Networks Network Security Architect (NetSec-Architect) Practice Tests
- Palo Alto Networks NetSec-Architect Practice Test 54 - 10 Questions (Last Reviewed 27-Sep-2026)
- Palo Alto Networks NetSec-Architect Practice Test 55 - 10 Questions (Last Reviewed 26-Sep-2026)
- Palo Alto Networks NetSec-Architect Practice Test 56 - 10 Questions (Last Reviewed 25-Sep-2026)
- Palo Alto Networks NetSec-Architect Practice Test 57 - 10 Questions (Last Reviewed 20-Nov-2026)
- Palo Alto Networks NetSec-Architect Practice Test 58 - 10 Questions (Last Reviewed 19-Nov-2026)