Home › GCP Associate Cloud Engineer › cloudcomputing › gcpsetup › Which approach correctly captures Google Cloud's…
Which approach correctly captures Google Cloud's quota model for compute resources?
AQuotas are per-project, per-region (or global), and can be raised by submitting a request to Google through the Cloud Console
BQuotas are set by the user once at organization creation and cannot ever change
CQuotas are global across all projects in an organization and cannot be raised
DQuotas apply only to free-tier accounts and disappear after the first invoice
Answer & Solution
Correct answer: A. Quotas are per-project, per-region (or global), and can be raised by submitting a request to Google through the Cloud Console
Google Cloud quotas are scoped per project per region (with some global quotas) and can be raised by submitting a request through the Quotas page. They aren't org-wide, don't disappear after billing starts, and can change throughout an account's lifetime.
Related questions
An organization wants every project in a specific folder to automatically inherit a policyWhich IAM role type lets you define the exact list of permissions you want, instead of relA team wants to grant a contractor read-only access to a single Cloud Storage bucket and nCloud Identity vs Google Workspace — which statement is correct?A new application needs to call the BigQuery and Cloud Storage APIs in a project. The APIsWhich mechanism on Google Cloud lets a central admin enforce a rule like "no externally acWhich Google Cloud principal type is meant to authenticate workloads (e.g. a Compute EnginWhich Google Cloud Identity and Access Management (IAM) concept defines a SET of permissio