> For the complete documentation index, see [llms.txt](https://atomoh.gitbook.io/kubernetes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atomoh.gitbook.io/kubernetes/en/quiz-collection/eks-hybrid-nodes/07-node-lifecycle-quiz.md).
# Node Lifecycle Management Quiz
> This quiz tests your understanding of the [Node Lifecycle Management](/kubernetes/en/amazon-eks/eks-hybrid-nodes/07-node-lifecycle.md) document.
***
1. What is the primary purpose of setting `systemReserved` and `kubeReserved` in the NodeConfig kubelet configuration?
* A) To automatically adjust pod resource requests
* B) To reserve resources for system processes and Kubernetes components to ensure node stability
* C) To increase the total resources available on the node
* D) To determine pod scheduling priority
Show Answer
**Answer: B) To reserve resources for system processes and Kubernetes components to ensure node stability**
**Explanation:** `systemReserved` reserves resources for the OS and system daemons (sshd, udev, etc.), while `kubeReserved` reserves resources for kubelet and containerd. This prevents pods from consuming all node resources, maintaining node stability.
***
2. What is the difference between kubelet's `evictionHard` and `evictionSoft`?
* A) `evictionHard` is a soft limit and `evictionSoft` is a hard limit
* B) `evictionHard` triggers immediate eviction, while `evictionSoft` evicts after a grace period
* C) `evictionHard` only evicts pods, while `evictionSoft` shuts down the node
* D) Both settings behave identically with only different names
Show Answer
**Answer: B) `evictionHard` triggers immediate eviction, while `evictionSoft` evicts after a grace period**
**Explanation:** When the `evictionHard` threshold is reached, kubelet immediately evicts pods. `evictionSoft` only evicts when the threshold persists for the duration specified in `evictionSoftGracePeriod`, preventing abrupt pod terminations.
***
3. According to the Kubernetes version skew policy, what is the oldest kubelet version that can run when the EKS control plane is at version 1.31?
* A) 1.27
* B) 1.28
* C) 1.29
* D) 1.30
Show Answer
**Answer: B) 1.28**
**Explanation:** According to the Kubernetes version skew policy, kubelet may be up to three minor versions older than the API server. With the API server at 1.31, kubelet is compatible with 1.31, 1.30, 1.29, and 1.28. Version 1.27 is n-4 and not supported.
***
4. What is the core principle of the canary upgrade strategy?
* A) Upgrade all nodes simultaneously
* B) Upgrade one node first, validate, then proceed with the rest
* C) Delete nodes and create new ones
* D) Perform in-place upgrades with zero downtime
Show Answer
**Answer: B) Upgrade one node first, validate, then proceed with the rest**
**Explanation:** A canary upgrade upgrades a single "canary" node first and validates the result. If no issues are found, a rolling upgrade proceeds for the remaining nodes, minimizing risk.
***
5. What label does nodeadm automatically assign when initializing hybrid nodes?
* A) `node-role.kubernetes.io/hybrid=true`
* B) `topology.kubernetes.io/zone=on-premises`
* C) `eks.amazonaws.com/compute-type=hybrid`
* D) `kubernetes.io/os=hybrid`
Show Answer
**Answer: C) `eks.amazonaws.com/compute-type=hybrid`**
**Explanation:** nodeadm automatically assigns the `eks.amazonaws.com/compute-type=hybrid` label during hybrid node initialization. This label does not need to be manually added to `--node-labels` and is used for Cilium affinity, workload placement, and more.
***
6. What is the correct action when an SSM Hybrid Activation has expired?
* A) Extend the expiration date of the existing activation
* B) Create a new SSM Hybrid Activation and update nodeconfig.yaml
* C) Switch to IAM Roles Anywhere
* D) Restart kubelet for automatic renewal
Show Answer
**Answer: B) Create a new SSM Hybrid Activation and update nodeconfig.yaml**
**Explanation:** SSM Hybrid Activations cannot have their expiration dates extended once expired. You must create a new activation, update the `activationCode` and `activationId` in nodeconfig.yaml, and re-register nodes if necessary.
***
7. What is the correct order for upgrading Kubernetes components?
* A) Upgrade nodes first, then the control plane
* B) Upgrade the control plane and nodes simultaneously
* C) Upgrade the control plane (EKS) first, then upgrade nodes
* D) The order does not matter
Show Answer
**Answer: C) Upgrade the control plane (EKS) first, then upgrade nodes**
**Explanation:** According to the Kubernetes version skew policy, kubelet cannot be newer than the API server. You must always upgrade the control plane first, then upgrade nodes. Upgrading nodes before the control plane causes compatibility issues.
***
8. If `shutdownGracePeriod: 60s` and `shutdownGracePeriodCriticalPods: 20s` are configured, how much termination grace time do regular pods receive?
* A) 20 seconds
* B) 40 seconds
* C) 60 seconds
* D) 80 seconds
Show Answer
**Answer: B) 40 seconds**
**Explanation:** `shutdownGracePeriodCriticalPods` is included within `shutdownGracePeriod`. Subtracting the 20 seconds reserved for critical pods from the total 60-second grace period leaves 40 seconds for regular pod termination. Critical pods (with priority class system-cluster-critical or system-node-critical) are terminated during the final 20 seconds.