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 feature
uniform bucket-level access
Topic in 2 exam domains
- uniform bucket-level access · Feature
- Uniform bucket-level access · Feature
- uniform-bucket-level-access · Feature · Cloud Storage
Also called: Bucket Policy Only, constraints/storage.uniformBucketLevelAccess, uniform access, Uniform Bucket Level Access, universal bucket-level access
A Cloud Storage bucket setting that enforces bucket-level access controls and causes object-level ACL get requests to fail.
Where this appears on the exam
2 objectives in 1 of 5 domains
Related topics
FoundationsBuilding blocksThis topicBuilds on theseBuilds on theseAppliedApplication Default CredentialsFeatureIdentity and Access ManagementService
uniform bucket-level accessFeature
DatastreamServiceCloud StorageServiceBigQueryServiceCloud SQLServiceGoogle SecOpsServiceDatabase Migration ServiceServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- uniform bucket-level access is part of Cloud Storage From the official documentation: “To use IAM exclusively, enable uniform bucket-level access to disallow ACLs for all Cloud Storage resources.”
- uniform bucket-level access secures Cloud Storage From the official documentation: “[Uniform bucket-level access](/storage/docs/uniform-bucket-level-access) allows you to uniformly control access to your Cloud Storage resources.”
- uniform bucket-level access depends on Identity and Access Management From the official documentation: “Uniform bucket-level access lets you only use bucket-level Identity and Access Management (IAM) permissions to grant access to your Cloud Storage resources.”
- 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.”
- 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 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.”
- BigQuery works with Datastream From the official documentation: “Permissions needed for datastream to write to BigQuery.”
- Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Cloud Storage works with Datastream From the official documentation: “When you stream to Cloud Storage, Datastream organizes data by object name and timestamp.”
- 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 SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- 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.”
- 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.”
- 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).”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Cloud SQL works with Datastream From the official documentation: “This page describes an example NAT VM configuration that lets Datastream privately connect to a Cloud SQL instance.”
- 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.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Database Migration Service depends on Cloud SQL From the official documentation: “For heterogeneous Oracle migrations to Cloud SQL, Database Migration Service requires that you first create and configure your Cloud SQL destination instance.”
- Google SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- 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).”
- 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.”
- 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 Google SecOps From the official documentation: “This document describes how fields of Cloud SQL context logs map to Google Security Operations Unified Data Model (UDM) fields.”
- Database Migration Service depends on Cloud Storage From the official documentation: “If you use file export and import to migrate, or use the Database Migration Service migration tool, you need to create a Cloud Storage bucket.”
- Google SecOps works with Identity and Access Management From the official documentation: “Test connectivity to the Identity and Access Management service with parameters provided at the integration configuration page in the Google Security Operations Marketplace tab.”
- Identity and Access Management secures Datastream From the official documentation: “You can get and set permissions for Datastream using the Google Cloud Console, the IAM methods of the API, or the Google Cloud SDK.”
How learners score on this topic
Last updated