Question 980
Original unofficial Palo Alto Networks NetSec-Architect scenario: A retailer’s cloud network is highly dynamic and the team manually adds every new workload to an appliance’s static address group. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A retailer’s cloud network is highly dynamic and the team manually adds every new workload to an appliance’s static address group. Governing principle: Cloud workloads can scale and readdress faster than static policy objects are updated. The most defensible design response is: Evaluate supported cloud-native dynamic integration and identity-based object discovery for the selected NGFW form factor. Validation: A newly tagged approved workload is included in policy without an unsafe blanket network allowance. Sustained assurance: Audit cloud tags and dynamic group membership after autoscaling events
Incorrect Answers
This alternative is linked to the architecture category: choose vm-series versus cloud ngfw for public cloud architectures. The actual problem is that a retailer’s cloud network is highly dynamic and the team manually adds every new workload to an appliance’s static address group; the controlling distinction is: cloud workloads can scale and readdress faster than static policy objects are updated.
The suggested “Measure route and session restoration during availability-zone drills.” tests a different architectural concern: architect aws inspection insertion, gwlb, transit gateway and ha. Here, a retailer’s cloud network is highly dynamic and the team manually adds every new workload to an appliance’s static address group. Cloud workloads can scale and readdress faster than static policy objects are updated.
The proposed design “Trend route growth and hub performance as branches are added.” addresses this related architecture topic: architect azure ngfw insertion, load balancing and high resilience. The actual security gap is that a retailer’s cloud network is highly dynamic and the team manually adds every new workload to an appliance’s static address group. Cloud workloads can scale and readdress faster than static policy objects are updated.