A. It enables self-service infrastructure provisioning while supporting app-specific requirements and organizational standards.
B. It isolates application environments completely to maximize security and avoid shared resources.
C. It enforces one infrastructure setup for all applications to reduce management complexity.
D. It centralizes all deployments in one environment to improve control and visibility.
Explanation:
The main advantage of a platform engineering approach is balancing self-service for developers with organizational governance and standardization.
Option A is correct because platforms enable developers to provision infrastructure and application environments independently while embedding security, compliance, and operational guardrails. This ensures that applications with diverse needs (e.g., different scaling patterns, compliance requirements, or environments) can still operate within a unified governance framework.
Option B (isolation only) is sometimes required for compliance but does not address the broader benefit of balancing flexibility and standardization.
Option C forces uniformity, which reduces adaptability for varied workloads.
Option D (centralized deployments) reduces developer autonomy and scalability.
The platform approach enables golden paths, curated abstractions, and reusable services, allowing diverse applications to thrive while maintaining control. This balance is central to platform engineering’s goal of reducing cognitive load and improving developer productivity.
Reference:
― CNCF Platforms Whitepaper
― CNCF Platform Engineering Maturity Model
― Cloud Native Platform Engineering Study Guide