▸case-13 We need high-performance L3/L4 network filtering and mTLS between microservices without the CPU overhead of sidecar proxies in every Pod. Recommend a networking and security architecture. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 We need to distribute incoming HTTP user traffic across two EKS clusters in us-east-1 and us-west-2 with dynamic failover if one cluster becomes unhealthy. Outline the global traffic routing design. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 We are migrating away from deprecated PodSecurityPolicies on Kubernetes 1.28. Formulate a security policy migration strategy for our namespaces without breaking existing workloads. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 Our infrastructure team spends hours manually running terraform apply to create identical EKS clusters for every new tenant. Design a declarative, Kubernetes-native cluster provisioning system. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We have a single Ubuntu virtual machine and want to run a Nginx proxy alongside a Python backend using Docker Compose. Provide the docker-compose.yml file to run these two containers. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 We are moving from Jenkins push scripts to a pull-based GitOps deployment pattern for microservices. We want agents inside the cluster automatically pulling changes from Git repositories. Provide an architectural design document detailing repository structure and reconciliation loop mechanics. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 A primary cloud region hosting our Kubernetes cluster experienced an unrecoverable datacenter outage. Design an automated backup and disaster recovery architecture for stateful persistent volumes and cluster metadata. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 Our AWS EKS cloud bill jumped 40% last month due to overprovisioned CPU requests and unutilized worker nodes. Formulate a platform cost optimization and resource right-sizing plan. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 We are updating our node OS images and removing Docker Engine as the CRI runtime on Kubernetes 1.26+ worker nodes. Outline the runtime architecture transition. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 We are scaling our infrastructure to support HIPAA-compliant workloads across two cloud regions using EKS. Please create an architectural blueprint for our platform. In your plan, include a detailed breakdown of cluster topology, network boundary setup, GitOps repository layout and rollout strategy, plus a rollback and disaster recovery framework for staging and production. | pass→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 Our Prometheus instance runs out of memory because we store 12 months of high-cardinality metrics locally on node disk. Design a distributed long-term metrics storage architecture. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 To comply with SLSA framework requirements, we need to guarantee that only cryptographically signed container images can be scheduled onto our Kubernetes worker nodes. Design a supply chain security workflow. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 Our team wants to eliminate downtime during microservice deployments by shifting traffic gradually based on real-time HTTP error rate metrics rather than doing immediate rolling updates. Outline a progressive delivery deployment strategy. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 We need to manage complex PostgreSQL database failovers and backups inside Kubernetes using custom domain logic rather than manual scripts. Design a custom controller architecture. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 Our engineering team needs a multi-tenant Kubernetes deployment model to host microservices across staging and production. Please formulate a platform design guide for us. Your output should clearly lay out the multi-tenancy isolation model, RBAC and security policy architecture, progressive delivery deployment flow with continuous reconciliation, and cost-optimization autoscaling strategies. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 We need to prevent developers from deploying containers running as root or pulling images from unauthorized registries across our clusters. Outline a policy-as-code enforcement architecture. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 I want to set up a local Kubernetes environment on my macOS laptop to test a single container image using KinD. Provide the shell commands and configuration file needed to create this local single-node cluster. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 Developers struggle with complex Helm values files and kubectl commands, causing frequent deployment errors. Design an internal developer platform abstraction layer. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 Our background queue workers experience sudden bursts of high message volume in RabbitMQ. Standard CPU-based autoscaling responds too slowly. Outline an autoscaling architecture that scales Pods based on queue depth. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 We need to modernize our on-premise Kubernetes cluster networking and container security posture before migrating to a managed service. Outline a comprehensive migration and platform modernization architecture. Make sure to cover service mesh traffic routing, Pod security standards, automated admission control validation steps, and an observability monitoring stack. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 Our Java Spring Boot service running inside a Pod is throwing a NullPointerException in the UserController class at line 42 when processing user requests. Here is the stack trace. How do I fix this Java code bug? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 We store sensitive credentials in HashiCorp Vault, but developers keep trying to commit base64-encoded Kubernetes Secret manifests into Git. Provide an architectural solution that synchronizes Vault secrets into native cluster Secrets securely while adhering to GitOps. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |