Question 250
Original unofficial Palo Alto Networks NetSec-Architect scenario: A security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Which test result best demonstrates that the design meets its requirement?
Explanation
Correct Answer
Original fictional security architecture situation: A security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Governing principle: Log aggregation is only useful if records preserve source identity and chronology. The most defensible design response is: Define canonical timestamps, device IDs and schema mappings before connecting the managed logging export to the SIEM. Validation: A synthetic threat event correlates to its policy rule and source device in both systems. Sustained assurance: Regression-test parsing after connector or log schema updates
Incorrect Answers
The suggested “A test rule change follows its proper authority and produces a consistent auditable approval record.” tests a different architectural concern: architect strata cloud manager, strata logging service and cloud identity engine. Here, a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Log aggregation is only useful if records preserve source identity and chronology.
The proposed design “A packet capture shows protected log transport and the SIEM receives an attributed test event.” addresses this related architecture topic: recommend resilient strata logging service integrations and forwarding protocols. The actual security gap is that a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Log aggregation is only useful if records preserve source identity and chronology.
This alternative is linked to the architecture category: recommend resilient strata logging service integrations and forwarding protocols. The actual problem is that a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent; the controlling distinction is: log aggregation is only useful if records preserve source identity and chronology.