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
Binary Authorization
Topic in 4 exam domains
- Binary Authorization · Service · Google Cloud service
- Binary Authorization · Feature
Also called: Binary Authorization service, binary_authorization, binauthz, Google Cloud Binary Authorization
A Google Cloud service that provides centralized software supply-chain security and deploy-time policy enforcement for containerized workloads.
Where this appears on the exam
3 objectives in 3 of 5 domains
Related topics
FoundationsThis topicWorks alongsideBuilds on theseAppliedVPC Service ControlsServiceIdentity and Access ManagementService
Binary AuthorizationService
Cloud StorageServiceCloud DeployServiceCompute EngineServiceArtifact AnalysisServiceCloud Audit LogsServiceCloud BuildServiceCloud LoggingServiceArtifact RegistryServiceGKEServiceGoogle Kubernetes EngineServiceCloud RunServiceManaged Service for Apache AirflowServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Binary Authorization secures Cloud Run From the official documentation: “Binary Authorization is a software supply chain security product for GKE and Cloud Run.”
- Binary Authorization works with Cloud Build From the official documentation: “Cloud Build, which produces attestations and provenance that Binary Authorization can use for enforcement and monitoring.”
- Binary Authorization works with GKE From the official documentation: “Binary Authorization is disabled on a GKE cluster.”
- Artifact Analysis works with Binary Authorization From the official documentation: “With Binary Authorization, you may use Artifact Analysis to store attestors and attestations as notes and occurrences, respectively.”
- VPC Service Controls secures Binary Authorization From the official documentation: “By adding Binary Authorization to the security perimeter, VPC Service Controls can help protect these resources and services.”
- Binary Authorization secures Artifact Registry From the official documentation: “If you're using Artifact Registry to store your artifacts, we recommend that you configure controls to help you secure your artifact repositories, such as access control, data exfiltration prevention, vulnerability scanning, and Binary Authorization.”
- Binary Authorization works with Cloud Audit Logs From the official documentation: “This guide shows you how to view Binary Authorization for Cloud Run in Cloud Audit Logs.”
- Binary Authorization works with Cloud Run From the official documentation: “This guide shows you how to disable Binary Authorization for Cloud Run.”
- Binary Authorization secures GKE From the official documentation: “Binary Authorization is disabled on a GKE cluster.”
- Binary Authorization works with Google Kubernetes Engine From the official documentation: “Using Binary Authorization on Google Kubernetes Engine ensures that the MLLP adapter can only be deployed from a verified and signed container image.”
- Binary Authorization secures Google Kubernetes Engine From the official documentation: “This lab describes how to secure a GKE cluster using Binary Authorization.”
- Artifact Registry works with Cloud Build From the official documentation: “Builds your container and pushes it to Artifact Registry.”
- Artifact Analysis works with Artifact Registry From the official documentation: “Artifact Analysis scans new images when they're uploaded to Artifact Registry.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
- 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 Deploy works with Cloud Run From the official documentation: “Quickstart: Deploy an app to Cloud Run by using Cloud Deploy”
- Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
- Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
- Cloud Logging works with Managed Service for Apache Airflow From the official documentation: “You can use [Cloud Monitoring](/monitoring/docs) and [Cloud Logging](/logging/docs) with Managed Service for Apache Airflow.”
- 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 Storage works with Managed Service for Apache Airflow From the official documentation: “Managed Airflow associates a Cloud Storage bucket with your environment.”
- 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.”
- Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
- Cloud Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
- Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- VPC Service Controls secures Managed Service for Apache Airflow From the official documentation: “Managed Airflow can be selected as a secured service inside a VPC Service Controls perimeter.”
- Artifact Registry works with Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories.”
- Artifact Registry works with GKE From the official documentation: “In the next tutorial, you deploy those images from the Artifact Registry repository to a GKE cluster:”
- Artifact Registry works with Managed Service for Apache Airflow From the official documentation: “Don't modify or delete the images built by Managed Airflow in Artifact Registry or the repository itself.”
- Cloud Audit Logs works with Cloud Storage From the official documentation: “Use Cloud Audit Logs to generate logs for API operations performed in Cloud Storage.”
- Cloud Build works with Cloud Deploy From the official documentation: “The pipeline uses Cloud Build for CI and Cloud Deploy for CD.”
- Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
- Cloud Deploy works with Cloud Storage From the official documentation: “Delete the Cloud Storage buckets that Cloud Deploy created.”
- Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
- Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
- 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.”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- Identity and Access Management secures Cloud Deploy From the official documentation: “You can secure your Cloud Deploy resources using IAM in the following ways:”
- Managed Service for Apache Airflow depends on GKE From the official documentation: “Managed Airflow runs your workloads on GKE.”
- Managed Service for Apache Airflow works with VPC Service Controls From the official documentation: “When used with Managed Airflow, VPC Service Controls have several [known limitations](/vpc-service-controls/docs/supported-products#composer).”
- VPC Service Controls secures Artifact Registry From the official documentation: “If your VPC Service Controls settings are blocking access to Artifact Registry, you must add the Artifact Registry service to the service perimeter of your VPC Service Controls.”
- Artifact Analysis works with Cloud Build From the official documentation: “Cloud Build generates this metadata and Artifact Analysis stores the information if you use Cloud Build to build the image.”
- Artifact Analysis works with VPC Service Controls From the official documentation: “VPC Service Controls provides support for Artifact Analysis.”
- Cloud Build works with Managed Service for Apache Airflow From the official documentation: “Cloud Build synchronizes your development Managed Airflow environment with these new changes.”
- Cloud Deploy works with GKE From the official documentation: “Route Cloud Deploy events to GKE”
- Cloud Deploy works with Google Kubernetes Engine From the official documentation: “You might need to enable other APIs to use Cloud Deploy features, including Google Kubernetes Engine, Cloud Storage, and Cloud Build APIs.”
- Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
- Cloud Logging works with Google Kubernetes Engine From the official documentation: “As an example, if you are using GKE, you can [use Cloud Logging to query](/logging/docs/view/building-queries) for GKE cluster audit logs.”
- 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).”
- 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 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.”
- Managed Service for Apache Airflow depends on Artifact Registry From the official documentation: “Managed Airflow uses Artifact Registry service to manage container image repositories used by Managed Airflow environments.”
- 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.”
How learners score on this topic
Last updated