Which TWO of the following are true regarding Dataplex security? (Choose two)
Dataplex enforces access through IAM policy bindings at three granularities: lake, zone and asset, letting permissions be scoped precisely to the resource hierarchy rather than the whole project. This satisfies the stem's requirement for true security statements, since inherited roles cascade downward from lake to zone to asset.
Why this answer
Option A is correct because Dataplex enforces fine-grained access control through IAM policies that can be attached at the Lake, Zone, or Asset level, allowing administrators to grant roles such as roles/dataplex.viewer or roles/dataplex.editor scoped to specific resources. Option E is correct because Dataplex supports VPC Service Controls perimeter integration, letting organizations restrict access to Dataplex resources and mitigate data exfiltration by adding dataplex.googleapis.com to service perimeters. Option B is not correct because Dataplex relies on Google Cloud IAM and federated identity rather than per-asset passwords.
Option C is not correct because Dataplex respects and layers on top of existing Cloud Storage IAM permissions rather than ignoring them. Option D is not correct because Dataplex uses Google Cloud's existing authentication (Cloud Identity/Google Workspace, OAuth 2.0) instead of providing a separate authentication system.
Exam trap
GCP-ADP often tests the integration of Dataplex with IAM and VPC Service Controls, and candidates may mistakenly think Dataplex has its own authentication or ignores storage permissions.