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
Storage Object User
Topic in 1 exam domain
- Storage Object User · Concept
- Storage Object User · Feature · IAM role
Also called: objectUser role, roles/storage.objectUser, Storage Object User IAM role, `roles/storage.objectUser`
An IAM role that grants permissions to write to and access a Cloud Storage bucket.
Where this appears on the exam
1 subdomain in 1 of 5 domains
~15% of exam
Related topics
FoundationsBuilding blocksThis topicBuilds on theseBuilds on theseAppliedApplication Default CredentialsFeatureIdentity and Access ManagementServicePub/SubService
Storage Object UserConcept
Cloud StorageServiceCloud Storage bucketConceptCloud SQLServiceBigQueryServiceStorage Transfer ServiceServiceDataflowServiceGoogle SecOpsServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Storage Object User secures Cloud Storage From the official documentation: “This permission is required to let your source Cloud SQL for SQL Server instance to save exported backup files to the Cloud Storage bucket you create in the **destination project**.”
- Storage Object User secures Cloud Storage bucket From the official documentation: “To get the permissions that you need to upload objects from memory to a bucket, ask your administrator to grant you the Storage Object User (`roles/storage.objectUser`) IAM role on the bucket.”
- Storage Object User is part of Identity and Access Management From the official documentation: “This requires [the Storage Object User IAM role](/storage/docs/access-control/iam-roles#standard-roles) set on that service account.”
- Storage Object User is part of Cloud Storage From the official documentation: “In **Select a role**, select **Cloud Storage**, then select **Storage Object Admin** or **Storage Object User** role.”
- Storage Object User configures Storage Transfer Service From the official documentation: “You must grant the Storage Object User (`roles/storage.objectUser`) role to the service agent. This provides the required `storage.folders.create` permission.”
- 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”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Cloud Storage works with Storage Transfer Service From the official documentation: “Transfer data between Cloud Storage services such as AWS S3 and Cloud Storage.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
- Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
- 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 Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, 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 secures Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
- Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Cloud Storage works with Google SecOps From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
- Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps can export detailed `ingestion_metrics` tables to your BigQuery dataset.”
- BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Cloud Storage bucket is part of Cloud Storage From the official documentation: “Create a Google Cloud Storage bucket”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- Application Default Credentials works with Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
- Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Dataflow depends on Cloud Storage From the official documentation: “Begin by creating a Cloud Storage bucket using the Google Cloud console or Google Cloud CLI. The Dataflow pipeline uses this bucket as a temporary storage location.”
- Google SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- Pub/Sub works with Storage Transfer Service From the official documentation: “Storage Transfer Service provides [Pub/Sub notifications](/storage-transfer/docs/pub-sub-transfer) on a variety of events.”
- Storage Transfer Service depends on Application Default Credentials From the official documentation: “To authenticate to Storage Transfer Service, set up Application Default Credentials.”
- Storage Transfer Service depends on Cloud Storage From the official documentation: “Storage Transfer Service requires access to Cloud Storage buckets in order to move data into or between Cloud Storage buckets.”
- 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 Cloud Storage bucket From the official documentation: “BigQuery lets you load [Datastore](/datastore) entities from a Cloud Storage bucket into a BigQuery table for analysis.”
- BigQuery works with Storage Transfer Service From the official documentation: “If needed, you can load the full record of all transfer errors to BigQuery to check on files or evaluate errors that remained even after retries.”
- Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- Cloud SQL works with Cloud Storage bucket From the official documentation: “If you exported into a Cloud Storage bucket, you can also check the log file created by Cloud SQL in the bucket for information about export status.”
- Cloud SQL works with Dataflow From the official documentation: “Use Datastream to replicate changes from your MySQL instance to either BigQuery or Cloud Storage, and then use Dataflow or Managed Service for Apache Spark to bring the data into your Cloud SQL instance.”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- 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).”
- Cloud Storage bucket works with Dataflow From the official documentation: “Begin by creating a Cloud Storage bucket using Google Cloud CLI. This bucket is used as a temporary storage location by the Dataflow pipeline.”
- Cloud Storage bucket works with Storage Transfer Service From the official documentation: “You can use [Storage Transfer Service](/storage-transfer/docs/create-transfers) to transfer data between zonal buckets and other Cloud Storage buckets.”
- Dataflow depends on Cloud Storage bucket From the official documentation: “Create a Cloud Storage bucket by using the gcloud CLI. This bucket is used as a temporary storage location by the Dataflow pipeline.”
- Dataflow depends on Identity and Access Management From the official documentation: “Dataflow uses Identity and Access Management (IAM) for authorization.”
- Google SecOps works with Pub/Sub From the official documentation: “This script collects messages from Pub/Sub subscriptions and ingests the data to Google SecOps.”
- Google SecOps depends on Storage Transfer Service From the official documentation: “This feed source uses the Storage Transfer Service (STS) to transfer data from Azure storage to Google SecOps.”
- Google SecOps works with Storage Transfer Service From the official documentation: “This feed source uses the Storage Transfer Service (STS) to transfer data from Azure storage to Google SecOps.”
- 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 BigQuery From the official documentation: “Security in BigQuery is intrinsically linked to [Identity and Access Management (IAM)](/iam/docs/overview) in Google Cloud.”
How learners score on this topic
Last updated