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
Google Cloud service
Identity and Access Management
Topic in 23 exam domains
- Identity and Access Management · Service
- Identity and Access Management · Feature
- Identity and access management · Service
Also called: Cloud IAM, Google Cloud Identity Access and Management, Google Cloud Identity access management, Google Cloud Identity and Access Management, Google IAM, Google Identity and Access Management, IAM, Identity and Access Management (IAM) API
Google Cloud's access control service that establishes fine-grained permissions and roles.
Where this appears on the exam
16 objectives in 5 of 5 domains
~22% of exam
~25% of exam
Domain 3
Storing the data~20% of exam
~15% of exam
~18% of exam
Related topics
FoundationsThis topicWorks alongsideAppliedApplication Default CredentialsFeatureVPC Service ControlsService
Identity and Access ManagementService
customer-managed encryption keysFeatureCloud SQLServiceCloud LoggingServiceCloud StorageServiceDatabase Migration ServiceServiceCloud RunServiceBigQueryServiceSecret ManagerServiceFirestoreServiceBigtableServiceCloud DeployServiceCloud DNSServiceDataformServiceEventarcServiceCloud MonitoringServiceWorkflowsServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Identity and Access Management secures Database Migration Service From the official documentation: “You can get and set permissions for Database Migration Service using the Google Cloud console, the IAM methods of the API, or the Google Cloud CLI.”
- Identity and Access Management secures Firestore From the official documentation: “This page describes the IAM permissions and roles for Firestore.”
- 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).”
- Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
- 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 secures Eventarc From the official documentation: “Eventarc uses Identity and Access Management (IAM) for authorization.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Bigtable From the official documentation: “Bigtable uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Cloud Deploy From the official documentation: “You can secure your Cloud Deploy resources using IAM in the following ways:”
- Bigtable works with Identity and Access Management From the official documentation: “Bigtable uses [Identity and Access Management (IAM)](/iam) for access control.”
- Cloud DNS works with Identity and Access Management From the official documentation: “Cloud DNS supports IAM permissions at the project level and individual DNS zone level.”
- Cloud Run works with Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”
- Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Identity and Access Management secures Dataform From the official documentation: “Dataform uses [Identity and Access Management (IAM)](/iam/docs) for access control.”
- Identity and Access Management configures Secret Manager From the official documentation: “This page describes the Identity and Access Management (IAM) roles you can use to configure Secret Manager.”
- Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
- Identity and Access Management secures Workflows From the official documentation: “This page describes the Identity and Access Management (IAM) roles and permissions available to control access to Workflows resources.”
- Cloud Deploy depends on Identity and Access Management From the official documentation: “In addition to other Identity and Access Management permissions you need for using Cloud Deploy, you need the following permissions in order to perform additional actions that might be needed for a canary deployment:”
- Cloud DNS depends on Identity and Access Management From the official documentation: “Therefore, you must have the proper IAM roles and permissions to use managed DNS services in GDC.”
- Cloud Monitoring depends on Identity and Access Management From the official documentation: “To use Monitoring, you must have the appropriate [Identity and Access Management](/iam/docs/overview) (IAM) permissions.”
- Dataform depends on Identity and Access Management From the official documentation: “Dataform uses the following Google Cloud services that have their own quota limits: - [BigQuery](/bigquery/quotas) - [Identity and Access Management](/iam/quotas)”
- Dataform works with Identity and Access Management From the official documentation: “Dataform uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Cloud DNS From the official documentation: “Cloud DNS uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
- Identity and Access Management works with Workflows From the official documentation: “Workflows manages access and authentication using Identity and Access Management (IAM) roles and permissions.”
- Workflows depends on Identity and Access Management From the official documentation: “Workflows uses [IAM](/iam/docs/overview) for access control.”
- Firestore depends on Application Default Credentials From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Application Default Credentials works with Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- 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.”
- Cloud SQL works with Database Migration Service From the official documentation: “Migrating from Cloud SQL to AlloyDB for PostgreSQL using Database Migration Service”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Application Default Credentials works with Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- Application Default Credentials secures Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
- BigQuery works with Dataform From the official documentation: “You can define custom SQL commands for Dataform to run in BigQuery.”
- Bigtable depends on Application Default Credentials From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Cloud Logging works with customer-managed encryption keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
- Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- BigQuery works with Bigtable From the official documentation: “External BigQuery data source backed by Bigtable”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Cloud Run works with Eventarc From the official documentation: “Route Eventarc events to Cloud Run”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud Run works with Secret Manager From the official documentation: “You can integrate Secret Manager with other Google Cloud products such as Cloud Run.”
- Cloud Storage works with Database Migration Service From the official documentation: “Database Migration Service replicates data from SQL Server backup and transaction log files that you upload to a Cloud Storage bucket.”
- Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Cloud Deploy works with Cloud Run From the official documentation: “Quickstart: Deploy an app to Cloud Run by using Cloud Deploy”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
How learners score on this topic
Last updated