Level-2

You have a microservices-based application running on Kubernetes. One of the microservices, called "User Service," is experiencing increased traffic and requires scaling. What Kubernetes resource would you use to automatically scale the User Service based on CPU utilization?

• Deployment

• ReplicaSet

• Pod

• HorizontalPodAutoscaler

You have a stateful application that requires stable network identity and persistent storage. Which Kubernetes resource would you use to manage the deployment and lifecycle of the stateful application?

• Deployment

• StatefulSet

• DaemonSet

• ReplicationController

You want to expose a Kubernetes service externally and provide load balancing across multiple Pods. What Kubernetes resource would you use to achieve this?

• Ingress

• Service

• Deployment

• Pod

You have multiple Kubernetes clusters spread across different regions, and you want to manage and deploy applications consistently across all clusters. What Kubernetes resource would you use to achieve this?

• Deployment

• StatefulSet

• Namespace

• Helm Chart

You have a multi-container application where two containers need to share a local filesystem within a Pod. What Kubernetes feature allows you to achieve this?

• PersistentVolume

• PersistentVolumeClaim

• EmptyDir

• ConfigMap

You want to automatically schedule Pods based on custom application-specific requirements, such as GPU resources or specialized hardware. What Kubernetes feature allows you to define and enforce these scheduling rules?

• Taints and tolerations

• Node affinity

• Pod anti-affinity

• Resource quotas

You want to ensure that a Pod is only scheduled on a node that has a specific label. What Kubernetes feature would you use to enforce this requirement?

• Pod anti-affinity

• Node affinity

• Taints and tolerations

• Resource quotas

During a sprint planning meeting, the team realizes that they have underestimated the effort required for a user story. What should the team do?

• Extend the sprint duration to accommodate the additional work.

• Collaboratively re-estimate the user story with input from the entire team.

• Delegate the user story to a specific team member with the required expertise.

• Remove the user story from the sprint backlog and address it in a future sprint.

The team discovers a defect in the production environment that was not caught during testing. What should the team do?

• Assign blame to the team member responsible for the defect.

• Immediately roll back the entire system to a previous stable version

• Conduct a root cause analysis to identify the reason for the defect and implement preventive measures.

• Ignore the defect since it has already been deployed, and focus on new development.

The product owner decides to add new requirements to the project during the sprint. What should the team do?

• Reject the new requirements and continue with the existing sprint backlog.

• Adjust the sprint plan and estimate the additional work required for the new requirements.

• Accommodate the new requirements without any adjustments to the sprint plan.

• Escalate the situation to the scrum master and request their intervention.