Build and operate the data processing systems behind analytics and ML on Google Cloud, including BigQuery, Dataflow, and Pub/Sub, and track your readiness for the Professional Data Engineer exam.
Advanced
Prepare and test your skills
Advanced
Prepare and test your skills
Concept
IAM permissions
Topic in 3 exam domains
Also called: database-level IAM permissions, permissions
Fine-grained access control permissions used to regulate access to Google Cloud resources.
Where this appears on the exam
3 subdomains in 2 of 5 domains
Related topics
FoundationsBuilding blocksThis topicBuilds on theseAppliedIdentity and Access ManagementServiceIdentity and Access Management (IAM)ServiceIAM rolesConceptrolesConceptCloud StorageServiceBigtableServiceKnowledge CatalogService
IAM permissionsConcept
Google SecOpsServiceBigQueryServiceservice accountConceptPoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- IAM permissions is part of IAM roles From the official documentation: “IAM roles that apply to Cloud SQL and the permissions contained in each role.”
- IAM permissions is part of roles From the official documentation: “IAM permissions are [grouped into roles](/document-ai/docs/access-control/iam-roles), and you assign roles to users and groups.”
- IAM permissions secures BigQuery
- IAM permissions depends on roles From the official documentation: “Permissions are not granted directly to users; permissions are instead granted indirectly through roles, which group permissions.”
- Identity and Access Management configures IAM permissions From the official documentation: “You can use IAM to manage who can access your project and what they are allowed to do.”
- BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
- BigQuery works with Cloud Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
- BigQuery works with Bigtable From the official documentation: “BigQuery lets you query your Bigtable data from BigQuery.”
- BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
- Cloud Storage works with Google SecOps From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps can export detailed `ingestion_metrics` tables to your BigQuery dataset.”
- IAM roles is part of Identity and Access Management From the official documentation: “IAM roles give the principals permissions to perform tasks on your App Topology resources.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management (IAM) secures BigQuery From the official documentation: “BigQuery uses IAM for fine-grained access control.”
- service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Bigtable is an alternative to Cloud Storage From the official documentation: “If the joining data is in the gigabyte or terabyte range, use either Bigtable or Cloud Storage to merge the joining data to the driving data, depending on the nature of the data.”
- Cloud Storage works with Knowledge Catalog From the official documentation: “Knowledge Catalog is an intelligent governance solution for data and AI assets in Google Cloud. It provides a centralized inventory where you can discover, manage, and govern your data across Google Cloud data sources like BigQuery, Cloud Storage, Pub/Sub, and Spanner.”
- Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
- Google SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- IAM roles works with service account From the official documentation: “In this section, you designate the service account for the gateway proxies and assign them the correct IAM roles.”
- IAM roles configures service account From the official documentation: “2. [Grant the necessary Identity and Access Management roles](#grant-iam-roles) to your service account.”
- BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
- BigQuery works with service account From the official documentation: “The service account can be used by services, such as Cloud Run, to read and modify data in the BigQuery dataset.”
- Bigtable works with Cloud Storage From the official documentation: “For example, if you frequently write data to Bigtable from a Cloud Storage bucket in the `us-central1` (Iowa) region, create your Bigtable cluster in a zone within `us-central1`.”
- Bigtable works with Identity and Access Management (IAM) From the official documentation: “Bigtable uses [IAM](/iam) for access control.”
- Bigtable works with Knowledge Catalog From the official documentation: “Knowledge Catalog automatically catalogs metadata about Bigtable resources.”
- Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
- IAM roles secures Bigtable From the official documentation: “Access to your Bigtable tables is controlled by your Google Cloud project and the [Identity and Access Management (IAM) roles](/bigtable/docs/access-control#roles) that you assign to users.”
- IAM roles secures Cloud Storage From the official documentation: “**Fine-grained access control**: Control agent access to Cloud Storage precisely using [IAM roles](/storage/docs/access-control/iam-roles).”
- IAM roles is part of Google SecOps From the official documentation: “The Google SecOps platform supports predefined IAM roles as well as custom roles, which you can add as needed.”
- IAM roles is part of Identity and Access Management (IAM) From the official documentation: “To prevent test disruptions, ensure that your Identity and Access Management (IAM) roles, policies, and failover configurations are correctly set up.”
- IAM roles secures Knowledge Catalog From the official documentation: “To get the permissions that you need to use the Knowledge Catalog and Looker (Google Cloud core) integration, ask your administrator to grant you the following IAM roles on project where your Looker (Google Cloud core) instance resides:”
- Identity and Access Management secures BigQuery From the official documentation: “Security in BigQuery is intrinsically linked to [Identity and Access Management (IAM)](/iam/docs/overview) in Google Cloud.”
- Identity and Access Management secures Bigtable From the official documentation: “Bigtable uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Google SecOps From the official documentation: “You create IAM policies that define which users and groups have access to Google SecOps features.”
- Identity and Access Management (IAM) secures Cloud Storage From the official documentation: “Cloud Storage supports two methods for granting users access to your buckets and objects: Identity and Access Management (IAM) and access control lists (ACLs).”
- Identity and Access Management (IAM) configures Knowledge Catalog
- Identity and Access Management (IAM) configures roles From the official documentation: “IAM allows you to grant specific **roles** to users, groups, and service accounts, giving them the necessary **permissions** to perform their tasks.”
- Knowledge Catalog depends on Identity and Access Management From the official documentation: “Knowledge Catalog uses Identity and Access Management (IAM) for authorization.”
- service account depends on BigQuery From the official documentation: “Each feature view uses a service account to access the source data in BigQuery during sync.”
- service account is part of Google SecOps From the official documentation: “Each Google SecOps instance has a unique service account.”
How learners score on this topic
Last updated