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
Access Transparency
Topic in 2 exam domains
- Access Transparency · Service
- Access Transparency · Feature
Also called: AXT, Google Access Transparency
An administrative access control offering that provides visibility into actions taken by Google employees when accessing customer content stored in Google Cloud.
Where this appears on the exam
2 objectives in 2 of 5 domains
~22% of exam
Domain 3
Storing the data~20% of exam
Related topics
This topicBuilds on theseBuilds on theseApplied
Access TransparencyService
VPC Service ControlsServiceApplication Default CredentialsFeatureAccess Transparency logsConceptStorage Transfer ServiceServiceIdentity and Access ManagementServiceCloud LoggingServiceAccess ApprovalServiceCloud StorageServiceGemini EnterpriseServiceFirestoreServiceAlloyDBServiceBigQueryServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Access Approval is part of Access Transparency From the official documentation: “The bastion host feature uses the Access Approval feature of Access Transparency to let Google request access to your data.”
- Access Transparency secures Firestore From the official documentation: “Secure Firestore with centralized Google Cloud governance encompassing Identity and Access Management,VPC Service Controls (VPC-SC), Access Transparency,<br>Access Approval, Cloud Monitoring, and Cloud Logging.”
- Access Approval depends on Access Transparency From the official documentation: “If Access Transparency is disabled, the **Access Approval** UI may be inaccessible until Access Transparency is re-enabled.”
- Access Approval works with Access Transparency From the official documentation: “Approved<br>access requests are logged with Access Transparency logs that are linked to the<br>approval request.”
- Access Transparency secures AlloyDB From the official documentation: “You can use Access Approval and Access Transparency to control access to AlloyDB instances by Google personnel who support the service.”
- Access Transparency works with Gemini Enterprise From the official documentation: “This page provides an overview of the support that [Access Transparency](/assured-workloads/access-transparency/docs/overview) provides for Gemini Enterprise.”
- Access Transparency works with Storage Transfer Service From the official documentation: “# Access Transparency for Storage Transfer Service”
- Access Transparency logs is part of Access Transparency From the official documentation: “Access Transparency provides you with logs that capture the actions that Google personnel take when accessing your content.”
- 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.”
- AlloyDB depends on Application Default Credentials From the official documentation: “To authenticate to AlloyDB, 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.”
- 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.”
- AlloyDB works with Application Default Credentials From the official documentation: “To authenticate to AlloyDB, 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 Storage works with Storage Transfer Service From the official documentation: “Transfer data between Cloud Storage services such as AWS S3 and Cloud Storage.”
- Application Default Credentials secures Gemini Enterprise From the official documentation: “To authenticate to Gemini Enterprise, set up Application Default Credentials.”
- 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).”
- VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
- Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud Logging works with Storage Transfer Service From the official documentation: “Enable Cloud Logging for agentless transfers, or transfers from S3-compatible sources, with `--log-actions` and `--log-action-states`.”
- 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.”
- Storage Transfer Service depends on Application Default Credentials From the official documentation: “To authenticate to Storage Transfer Service, set up Application Default Credentials.”
- BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Gemini Enterprise From the official documentation: “The following table compares the two ways that you can import BigQuery data into Gemini Enterprise data stores.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Gemini Enterprise depends on Application Default Credentials From the official documentation: “To authenticate to Gemini Enterprise, set up Application Default Credentials.”
- Storage Transfer Service works with VPC Service Controls From the official documentation: “The Storage Transfer Service integration with VPC Service Controls has no known limitations.”
- VPC Service Controls secures Gemini Enterprise From the official documentation: “The API for Gemini Enterprise can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
- Access Approval secures Firestore From the official documentation: “Secure Firestore with centralized Google Cloud governance encompassing Identity and Access Management,VPC Service Controls (VPC-SC), Access Transparency,<br>Access Approval, Cloud Monitoring, and Cloud Logging.”
- Access Approval depends on Identity and Access Management From the official documentation: “Access Approval uses Identity and Access Management (IAM) for authorization.”
- AlloyDB works with BigQuery From the official documentation: “By integrating AlloyDB and BigQuery, you can achieve a seamless flow of data between your transactional database and your data warehouse, which supports real-time analytics and helps you build powerful interactive applications.”
- Application Default Credentials secures Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- BigQuery works with Firestore From the official documentation: “You can load data from a Firestore with MongoDB compatibility export into BigQuery, but only if you specified a `collection-ids` filter.”
- Firestore works with VPC Service Controls From the official documentation: “Because Firestore with MongoDB compatibility is compliant with VPC Service Controls, you can use this domain in VPC Service Controls scenarios.”
- 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 Gemini Enterprise From the official documentation: “Gemini Enterprise uses Identity and Access Management (IAM) for authorization.”
- 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.”
- Access Approval secures AlloyDB From the official documentation: “You can use Access Approval and Access Transparency to control access to AlloyDB instances by Google personnel who support the service.”
- AlloyDB works with Cloud Logging From the official documentation: “Database Migration Service and AlloyDB use Cloud Logging.”
- AlloyDB works with Cloud Storage From the official documentation: “For example, if you frequently write data to AlloyDB from a Cloud Storage bucket in the `us-central1` (Iowa) region, create your AlloyDB cluster in the `us-central1` region.”
- AlloyDB works with VPC Service Controls From the official documentation: “This page provides an overview of VPC Service Controls, a Google Cloud feature that integrates with AlloyDB to secure data and resources.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Logging From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
- 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.”
- 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.”
- BigQuery works with VPC Service Controls From the official documentation: “BigQuery integrates with VPC Service Controls to restrict access to your BigQuery resources from specific networks.”
- Cloud Logging is an alternative to Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs either in Cloud Logging or in a user-created Cloud Storage bucket.”
How learners score on this topic
Last updated