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
organization policies
Topic in 1 exam domain
- organization policies · Concept
- Organization policies · Feature
- organization policies · Feature
Also called: org policies, organisation policies, policy constraints
Rules applied across a resource hierarchy that govern configurations and enforce security and compliance constraints.
Where this appears on the exam
In 1 of 5 domains
~22% of exam
Related topics
This topicBuilds on theseBuilds on theseBuilds on theseApplied
organization policiesFeature
Identity and Access ManagementServiceIdentity-Aware ProxyServiceCloud RunServiceCompute EngineServiceGKEServiceGoogle Kubernetes EngineServiceCloud SQLServiceManaged Service for Apache AirflowServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- organization policies configures Cloud SQL From the official documentation: “This page describes how to add organization policies on Cloud SQL instances, to put restrictions on Cloud SQL at the project, folder, or organization level.”
- organization policies configures Identity-Aware Proxy From the official documentation: “Organization policies specifically and strictly control only IAP enablement and not other aspects of the IAP configuration.”
- Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
- Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
- Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Identity-Aware Proxy secures Cloud Run From the official documentation: “There are two ways to enable Identity-Aware Proxy for your Cloud Run services.”
- Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Identity-Aware Proxy secures Compute Engine From the official documentation: “Securing Compute Engine apps Enable IAP for Compute Engine apps.”
- Cloud SQL works with GKE From the official documentation: “[From an application running on GKE](/sql/docs/postgres/connect-kubernetes-engine)”
- Managed Service for Apache Airflow depends on Cloud SQL From the official documentation: “Managed Airflow uses Cloud SQL to run Airflow database.”
- Cloud Run works with Identity-Aware Proxy From the official documentation: “On the Cloud Run security page, find the checkbox for Identity-Aware Proxy (IAP).”
- Compute Engine is an alternative to Google Kubernetes Engine From the official documentation: “You can install MongoDB on a Compute Engine instance or you can deploy MongoDB on Google Kubernetes Engine.”
- Compute Engine works with Identity-Aware Proxy From the official documentation: “Set up a Compute Engine instance with IAP.”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- Identity and Access Management works with Identity-Aware Proxy From the official documentation: “The IAP API lets you to apply IAM permissions to individual resources in an IAP-secured project.”
- Managed Service for Apache Airflow depends on GKE From the official documentation: “Managed Airflow runs your workloads on GKE.”
- Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
- Cloud Run works with Google Kubernetes Engine From the official documentation: “Improved security: take advantage of automatic IAM JWT injection for more secure communication between GKE and Cloud Run.”
- 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).”
- Cloud SQL works with Google Kubernetes Engine From the official documentation: “The [Connecting from Google Kubernetes Engine](/sql/docs/sqlserver/connect-kubernetes-engine) page demonstrates how to configure and connect to Cloud SQL.”
- GKE works with Identity-Aware Proxy From the official documentation: “GKE users can implement<br>IAP following this<br>[guidance](/iap/docs/enabling-kubernetes-howto)”
- Google Kubernetes Engine depends on Compute Engine From the official documentation: “Other products, such as [Google Kubernetes Engine](/kubernetes-engine) and [Dataflow](/dataflow), use Compute Engine resources and therefore, can be deployed in the same regions or zone.”
- Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Managed Service for Apache Airflow From the official documentation: “For access control, use Identity and Access Management and Managed Airflow [roles and permissions](/composer/docs/composer-2/access-control#user-account).”
- Identity-Aware Proxy secures GKE From the official documentation: “Securing Google Kubernetes Engine apps Enable IAP for GKE apps.”
- Identity-Aware Proxy works with Managed Service for Apache Airflow From the official documentation: “In VPC Service Controls mode, Managed Airflow runs two instances of the Airflow web server. Identity-Aware Proxy load balances user traffic between these instances.”
- Managed Service for Apache Airflow depends on Google Kubernetes Engine From the official documentation: “Managed Airflow depends on GKE to deliver support for non-RFC 1918 addresses for Pods and Services.”
- Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
- Cloud Run is an alternative to Compute Engine From the official documentation: “The decision of whether to use Cloud Run, GKE, or Compute Engine as your application host involves trade-offs between configuration flexibility and management effort.”
- Cloud Run is an alternative to Google Kubernetes Engine From the official documentation: “Run agents locally or scale them globally using Runtime, Cloud Run, or Google Kubernetes Engine.”
- Cloud SQL works with Managed Service for Apache Airflow From the official documentation: “Managed Airflow updates the Airflow `airflow_db` connection to point to the new Cloud SQL database.”
- Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”
- Compute Engine works with Google Kubernetes Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
- GKE depends on Identity and Access Management From the official documentation: “GKE relies on and can be used with many other Google Cloud services, from IAM for access control to Cloud Billing for managing your costs.”
- GKE works with Managed Service for Apache Airflow From the official documentation: “Managed Airflow uses Google Kubernetes Engine service to create, manage and delete environment clusters where Airflow components run.”
- Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
- Identity and Access Management configures GKE From the official documentation: “First, as you would with most services on Google Cloud, you need to configure [IAM](/iam) roles in order to set up authorization on GKE.”
- Identity-Aware Proxy secures Google Kubernetes Engine From the official documentation: “Identity-Aware Proxy (IAP) is a cloud-native alternative to traditional VPNs that manages access to applications running in Cloud Run, App Engine, Compute Engine, and GKE.”
- Identity-Aware Proxy depends on Identity and Access Management From the official documentation: “When an application or resource is protected by IAP, it can only be accessed through the proxy by [principals](/iam/docs/overview#concepts_related_identity), also known as users, who have the correct [Identity and Access Management (IAM) role](/iam/docs/understanding-roles).”
- Managed Service for Apache Airflow depends on Identity and Access Management From the official documentation: “Managed Airflow uses [Identity and Access Management (IAM)](/iam) for access control.”
How learners score on this topic
Last updated