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.
A security engineer manages organization policies for an enterprise Google Cloud environment structured with the following resource hierarchy:
organizations/1001)
folders/2001)
folders/3001)
dev-backend (projects/4001)eng-shared-tools (projects/4002)The security engineer applies the following organization policy specification at the organization root for a list constraint:
name: organizations/1001/policies/compute.storageResourceUseRestrictions
spec:
rules:
- values:
deniedValues:
- under:folders/2001
No other organization policies or overrides have been applied at any folder or project level.
What is the effective policy evaluation for dev-backend and eng-shared-tools?
This option posits that inherited deniedValues in list constraints are dormant or non-enforcing unless child resources create a local policy that explicitly enables inheritance or merges rules.
reset: true or by setting explicit overrides.Google Cloud required opt-in policy enforcement where child projects defaulted to open/permissive states until an explicit local binding acknowledged ancestral constraints.
under:) AreA hierarchy subtree string is a specialized value format used in Google Cloud list constraints prefixed by under: (such as under:organizations/ID, under:folders/ID, or under:projects/ID). Its primary purpose is to apply policy rules broadly across a logical container and all existing or future child resources rooted beneath it, eliminating the operational overhead of listing every project ID individually.
organizations/1001). By default, child resources inherit policies from their parent containers.folders/2001, folders/3001, eng-shared-tools, nor dev-backend define local overriding policies, they directly inherit the constraint rule from organizations/1001.eng-shared-tools (projects/4002), it detects that the project is an immediate child of folders/2001. For dev-backend (projects/4001), it evaluates ancestry up through folders/3001 to folders/2001. Because both resources reside within the hierarchy subtree rooted at folders/2001, the rule evaluates to denied for both.under: prefix acts on the designated resource and every nested descendant in the subtree, regardless of nesting depth.folders/2001 automatically inherit the denial without requiring policy modifications.In Google Cloud Organization Policy hierarchy evaluation, list constraints evaluate against resource lineage. Because the subtree rule specifies under:folders/2001, all resources descended from folders/2001 inherit and match the denied value.
This option asserts that the under: prefix is shallow and restricts enforcement strictly to direct, first-generation child resources under a folder, thereby failing to cascade into nested subfolders such as folders/3001.
dev-backend, the policy engine traverses the entire resource ancestry path (dev-backend $\rightarrow$ folders/3001 $\rightarrow$ folders/2001 $\rightarrow$ organizations/1001). Because folders/2001 is an ancestor, the under:folders/2001 condition matches.under: prefix is not limited to a single level of hierarchy depth.Google Cloud enforced a non-recursive folder evaluation model where child containers automatically shielded their descendants from ancestral subtree constraints unless explicitly reapplied.
This option suggests that hierarchy subtree strings (under:) are invalid when set at the organization level and can only be evaluated if attached directly to the target root folder specified in the string.
under:folders/VALUE_A, under:organizations/VALUE_X, under:projects/VALUE_Y) are designed specifically to be configured at higher hierarchy nodes—including the organization root—to govern subordinate branches without having to bind policies at each branch.under:folders/... as a standard hierarchy subtree string when applied at the organization root via gcloud org-policies set-policy.roles/orgpolicy.policyAdmin at the organization level) to define targeted zone or branch policies centrally.under: filter at the organization level is fully supported and evaluates accurately down the tree.Google Cloud restricted the under: prefix strictly to intra-node references where a policy could only target resources lower than or equal to the immediate attachment point.
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