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
Artifact Registry
Topic in 4 exam domains
- Artifact Registry · Service
- Artifact registry · Service · GDC air-gapped service
Also called: Artifact Registry repositories, artifactregistry, Cloud Artifact Registry, GDC private Artifact Registry
A repository service used for managing and storing container images.
Where this appears on the exam
3 objectives in 3 of 5 domains
Related topics
FoundationsBuilding blocksThis topicWorks alongsideAppliedArtifact AnalysisServiceCompute EngineServicecustomer-managed encryption keysFeatureVPC Service ControlsServiceCMEKFeatureSecret ManagerServiceCloud StorageServiceCloud SQLServiceBigQueryService
Artifact RegistryService
Cloud BuildServiceWorkflowsServiceCloud NATServiceDataflowServiceCloud LoggingServicePrivate Google AccessFeatureCloud RunServiceManaged Service for Apache AirflowServiceGKEServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- 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.”
- Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
- customer-managed encryption keys secures Artifact Registry From the official documentation: “Artifact Registry also supports [organization policy constraints](/artifact-registry/docs/cmek#org-policy) that can require CMEK to protect resources.”
- Artifact Registry is an alternative to Cloud NAT From the official documentation: “You can download the image and push to Artifact Registry or use [Cloud NAT](/nat/docs/overview) to provide outbound internet access for certain private nodes.”
- 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.”
- Artifact Registry works with Private Google Access From the official documentation: “Clusters are automatically configured with [Private Google Access](/vpc/docs/private-google-access), which, for example, permits clusters to pull images from Artifact Registry.”
- 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.”
- CMEK secures Artifact Registry From the official documentation: “You use the CMEK keys to help protect your data in Artifact Registry and in Cloud Run.”
- 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.”
- Artifact Analysis secures Artifact Registry From the official documentation: “Turn on Artifact Analysis, which allows for security scanning, for your Artifact Registry repository.”
- Artifact Registry works with Cloud Logging From the official documentation: “Artifact Registry sends the following types of audit log data to Cloud Logging:”
- Artifact Registry secures Cloud Run From the official documentation: “You can use Artifact Registry together with other Google Cloud products and features to improve the security posture of developer workflows and tools, software dependencies, CI/CD systems used to build and deploy your software, and runtime environments such as Google Kubernetes…”
- Artifact Registry depends on Cloud Storage From the official documentation: “The registry service hosts your custom images in Cloud Storage under your Google Cloud project.”
- Artifact Registry works with Cloud Storage From the official documentation: “| Artifact Registry | Stored in Cloud Storage, for each data chunk | |”
- Artifact Registry is an alternative to Cloud Storage From the official documentation: “Re-upload the template or definition to Artifact Registry or Cloud Storage.”
- Artifact Registry works with Dataflow From the official documentation: “To use Artifact Registry with Dataflow, you must grant at least [Artifact Registry Writer access](/artifact-registry/docs/access-control#permissions) (`role/artifactregistry.writer`) to the [worker service account](#worker-service-account) that runs the Dataflow job.”
- Cloud Run depends on Artifact Registry From the official documentation: “Cloud Run function deployments use Artifact Registry to store artifacts and manage container images.”
- GKE depends on Artifact Registry From the official documentation: “When you create or update a cluster, GKE pulls container images for the Kubernetes system software running on the control plane and nodes from Artifact Registry repositories in the `pkg.dev` or the `gcr.io` domain.”
- 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”
- BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- 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 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 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.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud Run works with Secret Manager From the official documentation: “You can integrate Secret Manager with other Google Cloud products such as Cloud Run.”
- Managed Service for Apache Airflow works with Secret Manager From the official documentation: “You can [configure Secret Manager](/composer/docs/composer-3/configure-secret-manager) as your Airflow secrets backend.”
- Cloud Build works with Secret Manager From the official documentation: “You can substitute secrets from [Secret Manager](/secret-manager/docs) in Cloud Build.”
- 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 Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- CMEK secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
- customer-managed encryption keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
- Dataflow works with Managed Service for Apache Airflow From the official documentation: “Launch Dataflow pipelines with Cloud Composer”
- 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 Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
- 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 Run works with Workflows From the official documentation: “Route Workflows events to Cloud Run”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Cloud Storage works with Managed Service for Apache Airflow From the official documentation: “Managed Airflow associates a Cloud Storage bucket with your environment.”
- CMEK secures BigQuery From the official documentation: “Enable CMEK for BigQuery Tables”
- 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 Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- GKE works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
- BigQuery works with Managed Service for Apache Airflow From the official documentation: “You can use Managed Airflow to orchestrate services in your data pipelines, such as triggering a job in BigQuery or starting a Dataflow pipeline.”
- Cloud SQL works with Secret Manager From the official documentation: “Secret Manager attempts to update the credentials in your Cloud SQL instance.”
- Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
- CMEK secures Cloud Storage From the official documentation: “Enable CMEK for Cloud Storage Buckets”
- customer-managed encryption keys secures Secret Manager From the official documentation: “In Secret Manager, you can use a CMEK to protect data at rest.”
- VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
How learners score on this topic
Last updated