Which of the following would be considered an advantage of using abstract APIs when offering cloud service provisioning and management as platform services?
Answer(s): B
Abstract APIs are an essential component of platform engineering, providing a simplified interface for developers to consume infrastructure and cloud services without deep knowledge of provider- specific details. Option B is correct because abstractions allow platform teams to curate services with built-in guardrails, ensuring compliance, security, and operational standards are enforced automatically. Developers get the benefit of self-service and flexibility while the platform team ensures governance.Option A would slow down the process, defeating the purpose of abstraction. Option C removes guardrails, which risks security and compliance violations. Option D allows uncontrolled deployments, which can create chaos and undermine platform governance.Abstract APIs strike the balance between developer experience and organizational control. They provide golden paths and opinionated defaults while maintaining the flexibility needed for developer productivity. This approach ensures efficient service provisioning at scale with reduced cognitive load on developers.
-- CNCF Platforms Whitepaper-- CNCF Platform Engineering Maturity Model-- Cloud Native Platform Engineering Study Guide
What is the main benefit of using minimal base container images and SBOM attestation practices in CI/CD pipelines?
The use of minimal base container images and Software Bill of Materials (SBOM) attestation is a best practice for strengthening software supply chain security. Option B is correct because smaller base images contain fewer components, which inherently reduces the attack surface and the number of potential vulnerabilities. SBOMs, meanwhile, provide a detailed inventory of included libraries and dependencies, enabling vulnerability scanning, license compliance, and traceability.Option A is only a partial benefit, not the primary goal. Option C (maximum flexibility) contradicts the principle of minimal images, which deliberately restrict included software. Option D (reducing storage costs) may be a side effect but is not the core benefit in a security-focused context.By combining minimal images with SBOM practices, platform teams ensure stronger compliance with supply chain security frameworks, enable early detection of vulnerabilities in CI/CD pipelines, and support fast remediation. This is emphasized in CNCF security and platform engineering guidance as a way to align with zero-trust principles.
-- CNCF Supply Chain Security Whitepaper-- CNCF Platforms Whitepaper-- Cloud Native Platform Engineering Study Guide
A software development team is struggling to adopt a new cloud native platform efficiently. How can a centralized developer portal, such as Backstage, help improve their adoption process?
Answer(s): A
Developer portals like Backstage act as the single entry point for platform services, APIs, golden paths, and documentation. Option A is correct because centralizing access greatly reduces the friction developers face when trying to adopt a new platform. Instead of searching across fragmented systems or learning low-level Kubernetes details, developers can find everything in one place, including templates, service catalogs, automated workflows, and governance policies.Option B is irrelevant to platform adoption. Option C may foster community sharing but does not directly address adoption challenges. Option D contradicts platform engineering principles, which emphasize democratizing access and self-service rather than restricting tools to senior developers.By providing a unified experience, portals improve discoverability, consistency, and self-service. They reduce cognitive load and support the platform engineering principle of improving developer experience, making adoption of new platforms smoother and more efficient.
In a cloud native environment, what is one of the security benefits of implementing a service mesh?
A key advantage of using a service mesh is its ability to secure service-to-service communication transparently, without requiring application code changes. Option A is correct because service meshes (e.g., Istio, Linkerd) provide mutual TLS (mTLS) by default, ensuring both encryption in transit and authentication between services. This establishes a zero-trust networking model inside the cluster.Option B (scaling) is managed by Kubernetes (Horizontal Pod Autoscaler), not service mesh. Option C (logging) may be supported as an observability feature, but it is not the primary security benefit. Option D (IP allowlisting) is an outdated, less flexible mechanism compared to identity-based policies that meshes provide.Service meshes enforce security consistently across all services, support fine-grained policies, and ensure compliance without burdening developers with complex configurations. This makes mTLS a foundational benefit in cloud native platform security.
-- CNCF Service Mesh Whitepaper-- CNCF Platforms Whitepaper-- Cloud Native Platform Engineering Study Guide
Which of the following is a primary benefit of using Kubernetes Custom Resource Definitions (CRDs) in a self-service platform model?
Answer(s): C
Kubernetes Custom Resource Definitions (CRDs) extend the Kubernetes API by allowing platform teams to create and expose custom APIs without modifying the core Kubernetes API server code. Option C is correct because this extensibility enables teams to define new abstractions (e.g., Database, Application, or Environment resources) tailored to organizational needs, which developers can consume through a self-service model.Option A is incorrect because scaling and failover are handled by controllers or operators, not CRDs themselves. Option B is wrong because RBAC is still required for access control over custom resources. Option D is misleading because multi-cloud support depends on how CRDs and their controllers are implemented, not a built-in CRD feature.By leveraging CRDs, platform teams can standardize workflows, hide complexity, and implement guardrails, all while presenting developers with simplified abstractions. This is central to platform engineering, as it empowers developers with self-service APIs while maintaining operational control.
-- CNCF Platforms Whitepaper-- Kubernetes Extensibility Documentation-- Cloud Native Platform Engineering Study Guide
Post your Comments and Discuss Linux Foundation CNPA exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CNPA content, but please register or login to continue.