Question 640
While designing controls for this requirement—An organization blocks entire generative cloud tools and disrupts sanctioned low-risk productivity workflows—what limitation should the project not overlook?
Explanation
Correct Answer
This assumption is unsafe because a broad vendor block can create unnecessary business disruption without managing risky actions. It directly threatens the requirement: An organization blocks entire generative cloud tools and disrupts sanctioned low-risk productivity workflows. Confirm the relevant evidence—inventory sanctioned application functions, risk categories and sensitive data handling needs—before selecting define granular sanctioned SaaS usage and DLP policy rather than unconditional provider-wide blocks.
Incorrect Answers
The option applies in “A security policy is based on SaaS application category but cannot distinguish read-only access from file upload”. Confirm the relevant evidence—inspect application functions, HTTP methods and available SaaS control granularity—before selecting design activity-specific SaaS controls for uploads, downloads and sharing where supported. That evidence does not directly establish “A broad vendor block can create unnecessary business disruption without managing risky actions” for the scenario at hand.
Applying this option would direct attention to a shared administrator account logs into many SaaS tenants but policies depend solely on the provider hostname. In the reported design—an organization blocks entire generative cloud tools and disrupts sanctioned low-risk productivity workflows—the needed risk statement is a broad vendor block can create unnecessary business disruption without managing risky actions.
The distinct use case for this response is “A firm permits cloud-drive collaboration but wants only company-managed tenants accessible for upload”. The design should document the corresponding investigation and practical acceptance evidence. The present case instead calls for “A broad vendor block can create unnecessary business disruption without managing risky actions”.