Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise organization is establishing perimeter security and API governance across its Google Cloud resource hierarchy. A security engineer must implement controls to meet the following requirements:
Development folder from activating or consuming any unapproved Google Cloud APIs, ensuring only an explicit allowlist of authorized services (such as Compute Engine and Cloud Storage) can be used.Which combination of controls should the security engineer implement to satisfy these requirements?
constraints/gcp.restrictServiceUsage) list constraint at the Development folder level with an allowlist of approved service identifiers, and configure API key restrictions with IP address application restrictions and specific API target restrictions.The Restrict Service Usage constraint (constraints/gcp.restrictServiceUsage) is a predefined Google Cloud Organization Policy list constraint that controls which Google Cloud services and APIs can be enabled and used within a specific resource hierarchy container (Organization, Folder, or Project). In parallel, API Key Restrictions provide granular defense-in-depth controls for credentials by restricting requests based on client context (such as IP addresses, HTTP referrers, or mobile app fingerprints) and restricting target API invocation scope.
constraints/gcp.restrictServiceUsage at the Development folder with spec.rules.allow.values containing authorized service names (e.g., compute.googleapis.com, storage.googleapis.com) establishes an inheritance guardrail. Project owners within this folder cannot enable or make API calls to unapproved Google Cloud services, even if they possess project-level roles/serviceusage.serviceUsageAdmin privileges.Development folder automatically cascades down to all current and future projects in that folder.This approach uses native Google Cloud resource hierarchy guardrails for service enablement and follows security best practices for API credential scoping without requiring custom infrastructure proxies.
This option proposes using Google Cloud Armor to inspect and filter traffic to API enablement endpoints, and attempting to bind API keys directly to OAuth 2.0 client IDs and service accounts.
gcloud CLI.The goal was to protect a custom web application hosted behind an External HTTPS Load Balancer against SQL injection and cross-site scripting (XSS) attacks while using OAuth 2.0 for user authentication.
Development folder blocking the serviceusage.services.enable permission, and configure API keys with HTTP referrer restrictions without API target restrictions.This configuration attempts to use IAM Deny policies to block the serviceusage.services.enable permission across the folder hierarchy, while using HTTP referrer (website) restrictions on the API key.
serviceusage.services.enable only blocks explicit service activation; it does not block access if services were enabled prior to the policy or activated via dependent service workflows. The predefined constraints/gcp.restrictServiceUsage constraint is the purpose-built mechanism to govern both enablement and runtime API usage.The scenario specifically required preventing users from modifying IAM role bindings for service activation while securing public single-page web applications (SPAs) running in end-user browsers.
Development folder projects with unrestricted service access, and configure API keys using Android application fingerprint restrictions.This option sets up a VPC Service Controls (VPC SC) perimeter around projects in the folder without restricting service APIs, and assigns Android application restrictions (SHA-1 fingerprint and package name) to the API keys.
The workloads consisted of mobile client applications running on Android devices accessing VPC-protected storage buckets across secure boundary bridges.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated