FirstTry

Objective 1.1

PCDE

Designing the overall resource hierarchy for an organization

Objective 1.1 sits in Bootstrapping and maintaining a Google Cloud organization, which carries 20% of the Cloud DevOps Engineer exam. The questions below are original, written from the official objective title above, and each explanation cites the Google Cloud page it rests on.

Objective title verbatim from the official objectives. Google Cloud exam page ↗

A worked example

Shown solved, with the whole explanation open: this is what every question here carries.

1-1Bootstrapping and maintaining a Google Cloud organization

Your company has a Cloud Identity account and an organization resource. A managed user creates a project without naming a parent. Where does that project land?

It is created but stays in a pending stateNothing is held pending. A new project reports lifecycle state ACTIVE, with ownership granted immediately to whoever created it.
It is created outside any organization resourceManaged accounts are barred from that outcome; only free trial and free tier users hold projects at the top of a hierarchy.
It defaults to the user's home organization resourceCorrect · your answerCorrect: the fallback parent is the account's own organization.
Creation fails until a parent folder is chosenFolders are an optional grouping mechanism, so a project needs no folder in place before it can exist.

Correct.

Concept

Membership of a managed domain constrains where new resources may live. Identity provisioning and resource placement are linked, so an account tied to a domain cannot mint objects that sit outside that domain's tree.

Why C

Accounts in the domain cannot create projects unaffiliated with an organization resource. Absent an explicit parent and the permission to choose one, placement falls back to the organization the account belongs to.

Source

Managed users (members of the account domain) must create projects within an organization. It's not possible for accounts associated with an organization resource to create project resources that aren't associated with an organization resource. By default, new projects belong to the organization associated with the user. If a user has the appropriate permissions, they can specify a different organization resource during project creation; otherwise, it defaults to their home organization.

Google Cloud: About resource hierarchy, checked August 2026
#resource-hierarchy#projects#cloud-identity

Now you: objective 1.1 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

1-1Bootstrapping and maintaining a Google Cloud organization

A company runs two Cloud Identity accounts and wants both of them to feed a single organization resource. What limit blocks that plan?

Sample question 2 of 3

1-1Bootstrapping and maintaining a Google Cloud organization

After an organization resource is provisioned for a domain, which roles does its initial allow policy grant to the entire Workspace domain?

Sample question 3 of 3

1-1Bootstrapping and maintaining a Google Cloud organization

An engineer inherits a project that has no organization above it. What becomes possible for that project once the domain gains an organization resource?

Full Cloud DevOps Engineer question bank coming

We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.

Read the sources

These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.

More objectives in Bootstrapping and maintaining a Google Cloud organization