Question 710
Original unofficial Palo Alto Networks NetSec-Architect scenario: A cloud collaboration suite supports both company tenant and personal accounts, but the company’s web rule allows them indistinguishably. Which test result best demonstrates that the design meets its requirement?
Explanation
Correct Answer
Original fictional security architecture situation: A cloud collaboration suite supports both company tenant and personal accounts, but the company’s web rule allows them indistinguishably. Governing principle: An application hostname is not necessarily enough to distinguish tenant trust. The most defensible design response is: Apply supported tenant-aware SaaS controls to distinguish corporate destinations from personal instances. Validation: A managed user can upload to the sanctioned business tenant but not to a personal tenant. Sustained assurance: Retest tenant restrictions as the SaaS provider changes login behavior
Incorrect Answers
The suggested “The connector is restricted until data classes, authorization and destinations are reviewed.” tests a different architectural concern: design saas application sanctioning and activity-level usage controls. Here, a cloud collaboration suite supports both company tenant and personal accounts, but the company’s web rule allows them indistinguishably. An application hostname is not necessarily enough to distinguish tenant trust.
“A test publicly shared sensitive file is identified despite the provider’s storage encryption.” concerns the separate design topic: differentiate saas security inline, saas api, sspm and enterprise dlp. It would not fix the described weakness: a cloud collaboration suite supports both company tenant and personal accounts, but the company’s web rule allows them indistinguishably. An application hostname is not necessarily enough to distinguish tenant trust.
This alternative is linked to the architecture category: differentiate saas security inline, saas api, sspm and enterprise dlp. The actual problem is that a cloud collaboration suite supports both company tenant and personal accounts, but the company’s web rule allows them indistinguishably; the controlling distinction is: an application hostname is not necessarily enough to distinguish tenant trust.