Container and Microservices Deployment Flashcards

You need to implement GitOps for AKS deployments where the cluster state is continuously reconciled with a Git repository. Which tool is purpose-built for this pattern?

Answer: Flux CD or Argo CD deployed in the AKS cluster

Flux CD and Argo CD are GitOps operators that run inside Kubernetes and continuously reconcile cluster state with the desired state declared in a Git repository.

A container in AKS keeps being OOMKilled. What is the correct resource configuration change to prevent this?

Answer: Increase the memory limit in the container's resources.limits.memory field

OOMKilled occurs when a container exceeds its memory limit; increasing resources.limits.memory gives the container more memory before the kernel terminates it.

In Azure Container Registry (ACR), which feature automatically removes untagged manifests and old image tags based on configurable retention policies?

Answer: ACR retention policies and automated purge tasks

ACR retention policies and scheduled purge tasks (az acr task create with a purge command) automatically clean up untagged manifests and old tags to manage registry storage.

When deploying microservices with Azure Container Apps, what is the purpose of the 'ingress' configuration with 'external: false'?

Answer: The container app is only reachable from other apps within the same Container Apps Environment

Setting external: false on a Container App's ingress restricts its HTTP endpoint to internal traffic within the Container Apps Environment, preventing public internet access.

You want Azure Pipelines to deploy to AKS only after a manual approval from the security team. Where is this approval gate configured?

Answer: On the Azure DevOps Environment as a pre-deployment approval check

Pre-deployment approvals are configured on Azure DevOps Environments; when a pipeline targets that environment, it pauses and waits for designated approvers before proceeding.

Which kubectl command shows the rollout history of a Deployment in AKS, including change-cause annotations from previous updates?

Answer: kubectl rollout history deployment/

kubectl rollout history lists revision numbers and their associated change-cause annotations, providing an audit trail of Deployment updates.

Your team needs to enforce a policy that all AKS containers must have CPU and memory resource limits defined. Which mechanism enforces this at admission time?

Answer: Azure Policy with the 'Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits' built-in

Azure Policy for AKS uses OPA Gatekeeper to deny pod admission if containers lack required CPU and memory resource limits, enforcing compliance before workloads run.