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 Approval
Topic in 2 exam domains
- Access Approval · Service
- Access Approval · Feature
An administrative access control offering ensuring that Google employees require explicit customer approval before accessing content stored on Google Cloud.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsThis topicWorks alongsideAppliedAccess TransparencyServiceIdentity and Access ManagementServiceApplication Default CredentialsFeatureCustomer-managed encryption keysFeature
Access ApprovalService
DataflowServicePub/SubServiceSecurity Command CenterServiceCloud LoggingServiceAssured WorkloadsServiceKey Access JustificationsFeatureGoogle Cloud ArmorServiceFirestoreServiceBigQueryServiceAlloyDBServiceCloud RunServicePoints 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 Approval works with Assured Workloads From the official documentation: “When used with<br>Assured Workloads, the Access Approval request<br>conditions are secondary to the applied Assured Workloads<br>personnel access assurances.”
- 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.”
- Access Approval works with Key Access Justifications From the official documentation: “For workloads with Access Approval enabled with a custom signing key, Key Access Justifications will also apply to processing signed access approval requests.”
- Access Approval works with Pub/Sub From the official documentation: “Customers are notified of a pending approval request using a preconfigured email or a Pub/Sub message.”
- 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 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.”
- Access Approval works with Google Cloud Armor From the official documentation: “Access Approval is available for regional Google Cloud Armor security policies.”
- Access Approval works with Security Command Center From the official documentation: “Access Approval supports the Security Command Center Premium tier.”
- Firestore depends on Application Default Credentials From the official documentation: “To authenticate to Firestore, 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.”
- Security Command Center depends on Application Default Credentials From the official documentation: “To authenticate to Security Command Center, set up Application Default Credentials.”
- Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials works with Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- AlloyDB works with Application Default Credentials From the official documentation: “To authenticate to AlloyDB, set up Application Default Credentials.”
- BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, 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 Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
- Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
- 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 Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
- BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Customer-managed encryption keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
- Customer-managed encryption keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
- Identity and Access Management secures Firestore From the official documentation: “This page describes the IAM permissions and roles for Firestore.”
- Application Default Credentials secures Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials works with Security Command Center From the official documentation: “To authenticate to Security Command Center, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- 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 Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
- Assured Workloads works with BigQuery From the official documentation: “After the enablement process is completed, you can use BigQuery in your<br>Assured Workloads folder.”
- BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Cloud Logging works with Security Command Center From the official documentation: “Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.”
- Cloud Run works with Firestore From the official documentation: “The Cloud Run app stores the result in Firestore.”
- 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.”
- 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 Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
- 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.”
- BigQuery works with Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
- Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
- Cloud Logging works with Dataflow From the official documentation: “Information stored in [Cloud Logging](/logging/docs/region-support) is primarily generated by the code in your Dataflow program.”
- 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).”
- Customer-managed encryption keys secures AlloyDB From the official documentation: “Enable customer-managed encryption keys (CMEK) in the AlloyDB cluster to gain more control over data encryption and key management.”
- Customer-managed encryption keys secures Cloud Logging From the official documentation: “Cloud Logging supports encrypting Log storage with CMEK keys.”
- Customer-managed encryption keys works with Security Command Center From the official documentation: “to learn about using customer-managed encryption keys (CMEKs) with Security Command Center.”
How learners score on this topic
Last updated