サンプル問題 1： What is the goal of automating processes in platform teams?
A: Reducing time spent on repetitive tasks.
B: Focusing on manual processes.
C: Increasing the number of tasks completed.
D: Ensuring high-quality coding standards.
正解：A
Explanation: Comprehensive and Detailed Explanation at least 150 to 200 words: In platform engineering, automation’s primary goal is to eliminate manual, repetitive toil by codifying repeatable workflows and guardrails so teams can focus on higher-value work. Authoritative Cloud Native Platform Engineering guidance emphasizes that platforms should provide consistent, reliable, and secure self-service capabilities―achieved by automating provisioning, configuration, policy enforcement, and delivery pipelines. This directly reduces cognitive load and handoffs, shortens lead time for changes, decreases error rates, and improves overall reliability. While automation often improves code quality indirectly (e.g., through automated testing, linting, and policy-as-code), the central, explicitly stated aim is to remove repetitive manual work and standardize operations, not to simply “do more tasks” or prioritize manual intervention. Therefore, option A most accurately captures the intent. Options B and C misframe the objective: platform engineering seeks fewer manual steps and better outcomes, not just higher task counts. Option D is a beneficial consequence but not the core purpose. By systematizing common paths (“golden paths”) and embedding security and compliance controls into automated workflows, platforms deliver predictable, compliant environments at scale while freeing engineers to focus on product value. Reference: ― CNCF Platforms Whitepaper (Platform Engineering) ― CNCF Platform Engineering Maturity Model ― Cloud Native Platform Engineering Study Guide
サンプル問題 2： Which of the following strategies should a team prioritize to enhance platform efficiency?
A: Encourage teams to handle all platform tools independently without guidance.
B: Implement manual updates for all cluster configurations.
C: Automate the version bump process (or cluster updates).
D: Conduct weekly meetings to discuss every minor update.
正解：C
Explanation: Comprehensive and Detailed Explanation at least 150 to 200 words: Enhancing platform efficiency requires reducing operational friction and ensuring that updates, patches, and upgrades happen consistently without introducing unnecessary manual effort or delays. According to Cloud Native Platform Engineering practices, automation of the version bump process―whether for libraries, services, or cluster configurations―is a critical strategy for improving both reliability and security. By automating cluster updates, teams can minimize human error, enforce standardized practices, and ensure systems remain aligned with compliance and security benchmarks. Option A, where each team independently manages platform tools, increases fragmentation and cognitive load, ultimately reducing efficiency. Option B, relying on manual updates, is both error-prone and unsustainable at scale, particularly in environments with multiple clusters or microservices. Option D, holding frequent meetings to discuss minor updates, wastes engineering cycles without delivering the tangible improvements that automation can achieve. Automating updates is a direct application of Infrastructure as Code and GitOps principles, enabling declarative management, reproducibility, and consistent rollout strategies. Additionally, automation supports zero-downtime upgrades, aligns with cloud native resilience patterns, and improves developer experience by abstracting away operational complexity. Thus, option C represents the most effective strategy for enhancing platform efficiency. Reference: ― CNCF Platforms Whitepaper (Platform Engineering) ― CNCF GitOps Principles for Platforms ― Cloud Native Platform Engineering Study Guide
サンプル問題 3： In a multi-cluster Kubernetes setup, which approach effectively manages the deployment of multiple interdependent applications together as a unit?
A: Employing a declarative application deployment definition.
B: Creating separate Git repositories per application.
C: Direct deployments from CI/CD with Git configuration.
D: Using Helm for application packaging with manual deployments.
正解：A
Explanation: In multi-cluster Kubernetes environments, the challenge lies in consistently deploying interdependent applications across clusters while ensuring reliability and repeatability. The Cloud Native Platform Engineering guidance stresses the importance of a declarative approach to define applications as code, which enables teams to describe the entire application system―including dependencies, configuration, and policies―in a single manifest. This ensures that applications are treated as a cohesive unit rather than isolated workloads. Option A is correct because declarative application deployment definitions (often managed through GitOps practices) allow for consistent and automated reconciliation of desired state versus actual state across multiple clusters. This approach supports scalability, disaster recovery, and compliance by ensuring identical deployments across environments. Option B (separate repos per application) increases fragmentation and does not inherently manage interdependencies. Option C (direct deployments from CI/CD) bypasses the GitOps model, which reduces auditability and consistency. Option D (Helm with manual deployments) partially addresses packaging but lacks the automation and governance needed in a multi-cluster setup. Reference: ― CNCF GitOps Principles for Platforms ― CNCF Platforms Whitepaper ― Cloud Native Platform Engineering Study Guide
