Question 1030
Original unofficial Palo Alto Networks NetSec-Architect scenario: A cloud workload uses certificate pinning and breaks when the security team enables inbound or forward-proxy inspection broadly. Which test result best demonstrates that the design meets its requirement?
Explanation
Correct Answer
Original fictional security architecture situation: A cloud workload uses certificate pinning and breaks when the security team enables inbound or forward-proxy inspection broadly. Governing principle: Pinned trust validation can reject intermediate inspection certificates by design. The most defensible design response is: Classify pinned services and use supported selective decryption with documented alternative detection and access controls. Validation: A pinned synthetic client operates without insecure bypass while approved decryptable traffic remains inspected. Sustained assurance: Test critical clients during certificate rotation and decryption changes
Incorrect Answers
The suggested “A short-lived TLS workload at expected peak shows no unacceptable handshake failures or latency.” tests a different architectural concern: evaluate ssl decryption inspection and performance tradeoffs. Here, a cloud workload uses certificate pinning and breaks when the security team enables inbound or forward-proxy inspection broadly. Pinned trust validation can reject intermediate inspection certificates by design.
The proposed design “The test connection’s forward and return packets traverse compatible inspection state throughout the session.” addresses this related architecture topic: design layer 3 routing, ecmp, bgp and ospf for protected flows. The actual security gap is that a cloud workload uses certificate pinning and breaks when the security team enables inbound or forward-proxy inspection broadly. Pinned trust validation can reject intermediate inspection certificates by design.
This alternative is linked to the architecture category: design layer 3 routing, ecmp, bgp and ospf for protected flows. The actual problem is that a cloud workload uses certificate pinning and breaks when the security team enables inbound or forward-proxy inspection broadly; the controlling distinction is: pinned trust validation can reject intermediate inspection certificates by design.