Your organization has recently onboarded Google Cloud. Dev team has approached you with a requirement to store, manage and secure their build artifacts. Which Google Cloud product would you suggest implementing?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: C.
Option A is incorrect.
Container Registry helps customers in Docker container storage and management securely.
Option B is incorrect.
Google Cloud product Knative is a Kubernetes-based platform for modern serverless workload build, deployment and management.
Option C is correct.
Artifact Registry is a Google Cloud product that helps store, manage and build artifacts securely.
Option D is incorrect.
Refer to the explanation of.
Option A and Option C above.
https://cloud.google.com/container-registry https://cloud.google.com/knative https://cloud.google.com/artifact-registryCertainly!
When it comes to storing, managing, and securing build artifacts in Google Cloud, there are a few options available. Let's go through each of them to see which one would be the best fit for this scenario.
A. Container Registry
Google Container Registry is a private container image registry that allows you to store and manage Docker container images. It integrates seamlessly with Google Kubernetes Engine (GKE) and other Google Cloud services. If your organization is already using containers and Kubernetes for its application deployments, then Google Container Registry could be a good option for storing your build artifacts. However, if your Dev team is not currently using containers, then it may not be the best fit.
B. Knative
Knative is a serverless platform that allows you to run containerized workloads on Kubernetes. While it has some features for managing build artifacts, it's primarily focused on running serverless workloads. Unless your Dev team is already using Knative for their application deployments, it's not likely to be the best option for storing build artifacts.
C. Artifact Registry
Google Artifact Registry is a private artifact repository that allows you to store a variety of build artifacts, including Docker images, Maven packages, and npm modules. It's a more general-purpose solution than Google Container Registry, and is designed to work with a wide range of build tools and programming languages. It also provides features for managing access control and permissions. Based on the requirements provided in the question, Google Artifact Registry would be the most suitable option for storing, managing and securing build artifacts.
D. Any of Option A or Option C
While both Google Container Registry and Google Artifact Registry can store build artifacts, each has its own set of strengths and weaknesses. If your Dev team is already using containers and Kubernetes for its application deployments, then Google Container Registry could be the better option. However, if you are looking for a more general-purpose solution that can handle a variety of build artifacts, then Google Artifact Registry would be the better option. Therefore, selecting either Option A or Option C would depend on your specific use case and requirements.