Kcna Kubernetes And Cloud Native Associate · Free Practice Question Easy

Question 5

When considering the security of credentials for a platform, which type of deployment is more secure?

  • A

    both push-based and pull-based deployments are equally secure

  • B

    push-based deployments

  • C

    pull-based deployments

  • D

    neither push-based nor pull-based deployments are secure

Reveal correct answer

Correct answer: C

Explanation

When using a pull-based deployment approach, all changes are made within the Kubernetes cluster itself. This approach has the benefit of enhanced security because it eliminates the need for external clients to have admin access to the cluster. This reduces the risk of attacks on the cluster and ultimately minimizes the cluster's attack surface.

If you decide to utilize a push-based deployment strategy for a k8s cluster, you'll have to reveal the system's credentials and save them in the CI system since it's an external system. The pipeline must have direct access to the cluster to make changes to production. However, this may put your environment at risk, so it's important to apply encryption and access controls to restrict who can access them. Additionally, rotating them frequently can help reduce the risk of compromise.

https://thenewstack.io/push-vs-pull-in-gitops-is-there-really-a-difference/

A. Both push-based and pull-based deployments have their own security considerations, but in general, pull-based deployments are considered more secure due to the reduced exposure of credentials during the deployment process. While both methods can be secure with proper security measures in place, pull-based deployments are often preferred for better security practices.

B. Push-based deployments involve pushing code and changes to the platform, which can potentially expose credentials during the process. This method may not be as secure as pull-based deployments because of the risk of credentials being leaked during the push process.

C. Pull-based deployments involve the platform pulling code and changes from a repository, which reduces the exposure of credentials during the deployment process. This method is considered more secure as it minimizes the risk of credential exposure compared to push-based deployments.

D. Neither push-based nor pull-based deployments are inherently insecure, but pull-based deployments are generally considered more secure due to the reduced risk of credential exposure during the deployment process. It is important to implement proper security measures regardless of the deployment method chosen to protect credentials effectively.

Discussion

Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.

You must be logged in to post a comment.

Preparing For

Your Certification?

255+ certifications
Detailed explanations
Free PDF samples

Has All The Questions You Need