Changed Professional-Cloud-Security-Engineer Exam Questions

Use Pub/Sub and Cloud Functions to trigger a Cloud Data Loss Prevention scan every time a file is uploaded to the administrator's bucket. If the scan does not detect PII, have the function move the objects into the shared Cloud Storage bucket:

Configure a Pub/Sub topic to publish notifications when new files are uploaded to the administrator's bucket.

Create a Cloud Function that is triggered by the Pub/Sub topic. This function uses the Cloud Data Loss Prevention (DLP) API to scan the uploaded files for PII.

If the scan does not detect PII, the function moves the file to the shared Cloud Storage bucket. This ensures that only non-sensitive data is accessible to analysts, while PII remains secure in the administrator's bucket.

To centrally govern and restrict which AI models (from the Model Garden) can be used within an organization, Google Cloud provides a specific Organization Policy Constraint.9

According to Google Cloud Documentation (Vertex AI Organization Policy Constraints):

"The constraints/vertexai.allowedModels constraint allows you to define a list of allowed models that can be deployed or used within your organization. This includes Google first-party models, open-source models, and third-party models available in the Model Garden.10 By using this policy, you can prevent users from using unvetted or non-compliant models even if they have IAM permissions to use Vertex AI."

How it works:

You define an "Allowlist" of model IDs.

When a user attempts to deploy a model or call an API for a model not on the list, the request is blocked.

This is the most scalable and compliant way to manage AI governance.

Why other options are incorrect:

A is incorrect: Model Garden is a catalog; you cannot apply granular IAM permissions to individual entries within the public catalog itself in the same way you can restrict API usage via Org Policy.

B is incorrect: Auditing is reactive. The requirement is to ensure users can only access approved models (prevention).

There is mention about simulating in Web Security Scanner. "Web Security Scanner cross-site scripting (XSS) injection testing *simulates* an injection attack by inserting a benign test string into user-editable fields and then performing various user actions."

The problem focuses on securing "super administrator accounts for the organization" when Cloud Identity is synced with Microsoft Entra ID and uses Entra ID for SSO. The key requirements are the principle of least privilege and strong authentication.

Principle of Least Privilege & Dedicated Accounts: Google's best practices strongly recommend creating dedicated, non-federated accounts for super administrators that are distinct from regular user accounts. These accounts should only be used for super administrator tasks and not for daily activities. This segregation ensures that the highest privilege accounts are isolated and adhere to the principle of least privilege by not having combined responsibilities.

Extract Reference: "Designate Organization Administrators... We recommend keeping your super admin account separate from your Organization Administrator group." and "Give super admins a separate account that requires a separate login. For example, user alice@example.com could have a super admin account alice-admin@example.com." and "Use the super admin account only when needed. Delegate administrator tasks to user accounts with limited admin roles. Use the least privilege approach..." (Google Cloud Documentation: "Super administrator account best practices | Resource Manager Documentation" -

Strong Authentication (Google 2-Step Verification): Even when using a third-party identity provider like Microsoft Entra ID for most users, Google recommends enforcing Google's own 2-Step Verification for the critical super administrator accounts. This provides a "break-glass" mechanism that is independent of the external IdP. If the Entra ID integration were to fail or become compromised, the Google-managed super administrator accounts, protected by Google's own 2SV, would still be accessible for emergency recovery.

Extract Reference: "Even when using the legacy SSO profile, super admins can't sign in with SSO in these cases: Admin console. When super administrators try to sign in to an SSO-enabled domain via admin.google.com, they must enter their full Google administrator account email address and associated Google password (not their SSO username and password), and click Sign in to directly access the Admin console. Google doesn't redirect them to the SSO sign-in page." (Google Cloud Identity Help: "Super administrator SSO" - - This highlights that super admin accounts can bypass SSO for direct Admin console access, making Google 's 2SV crucial.

Extract Reference: "It's especially important for super admins to use 2SV because their accounts control access to all business and employee data in the organization. Protect your business with 2-Step Verification. Use security keys for 2-Step Verification." (Cloud Identity Help: "Security best practices for administrator accounts" -

Options C and D are incorrect because combining "organization administrator" (IAM role for GCP resources) and "super administrator" (Google Workspace/Cloud Identity domain-level control) privileges violates the principle of least privilege. Option A is less secure than B because relying solely on Entra ID's 2SV for super administrators means a compromise of Entra ID or an outage would leave the Google Cloud organization vulnerable without an independent break-glass mechanism.