Who Created These Manually Provisioned Projects?

ACE By islever Editorial Last updated Oct 24, 2026

Setting up cloud projects and accounts. Managing Identity and Access Management (IAM).

Short answer

D Open the project's IAM page and locate the user holding the Owner role, since the project creator was granted Owner when the project was created.

Question

You are responsible for Google Cloud governance at your company and recently implemented a new, automated process for provisioning Google Cloud projects. You have discovered several projects that were manually created before the implementation of this new process. You need to identify the creators of these projects to inform them of the new process. What should you do?

Review the value of the creator label attached to the project to find the project’s creator.
Use Resource Manager to identify the responsible department from the folder and project hierarchy.
Review the Cloud Billing account linked to the project, and then contact the owner of that billing account.
Use the IAM page in the Google Cloud console to identify the user with the Owner role. Correct Answer

Key Takeaways

The question tests identifying a project's individual creator, and the trap is assuming a 'creator' label exists on projects that were created before any labeling process was in place.

This Google Cloud governance scenario asks how to trace the creators of projects created manually before an automated provisioning process existed. The page establishes that the IAM page's Owner role is the practical answer, because console-created projects grant the creating user Owner, while no automatic creator label, folder hierarchy, or billing owner reveals the individual.

Common mistake: Most learners choose A, believing Google Cloud attaches a creator label to every project; the platform does not create such a label automatically, and these manually created projects predate the automated process that would have added one.

Expert Analysis

Why the Answer Is Correct

When a user creates a project in the Google Cloud console, that user is granted the Owner role (roles/owner) on the new project by default. Opening the project's IAM page therefore surfaces the account that actually stood the project up, which is exactly the information needed to notify creators about the new provisioning process. This is the only option that exposes an individual identity rather than an organizational or financial attribute. It works even though no metadata field called 'creator' exists on Resource Manager projects. The approach gives you a concrete user principal you can contact directly.

Why the Other Options Are Wrong

Option A assumes a creator label is attached to the project, but Google Cloud never attaches one automatically, and these projects were manually created before the new automated process that might apply such labels existed. Option B only tells you which folder and therefore which department owns the project; the folder hierarchy records structure, not the identity of the person who created the project. Option C leads you to the billing account owner, who is typically a finance or platform administrator and is frequently a different person from the project creator. Neither B nor C yields an individual creator identity.

Community Comment Notes

Mr_MIXER007 selected D, arguing that the other choices fail outright while 'here at least one owner will definitely be there.' That reasoning matches the platform behavior: the creator receives Owner at creation time, so an Owner entry is a reliable pointer to them. The comment correctly dismisses the label, folder, and billing alternatives, though it is worth remembering that additional users may also hold Owner on the project.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

When a question asks you to identify a person or actor in Google Cloud and no audit-log option is offered, look for the option that exposes an individual IAM principal; labels, folders, and billing accounts describe things, not people. Rule out any option that presumes metadata exists that the platform does not create by default.

Frequently Asked Questions

Why is the creator label option wrong for these manually created projects?

Google Cloud does not attach a creator label automatically, and these projects predate the automated provisioning process that would have applied labeling conventions.

How does the IAM Owner role reveal the project creator?

When a project is created in the console, the creating user is granted the Owner role by default, so the Owner entries on the IAM page point back to the creator.

More ACE FAQ →

Discussion 1 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 1

Mr_MIXER007 👍 1 Answered D

D. Use the IAM page in the Google Cloud console to identify the user with the Owner role. Because other options won't help. But here at least one owner will definitely be there.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Practice All ACE Questions

Access 84 questions with complete answers and detailed explanations.

View Full ACE Practice Test →

← Back to ACE Study Guide