최신Linux Foundation Certified Cloud Native Platform Engineering Associate - CNPA무료샘플문제

A. Role-based access control (RBAC)

B. Pod Security Standards

C. Security Context

D. Network Policies

A. RBAC allows users to have unrestricted roles and access to all resources in the cluster.

B. RBAC does not support namespace isolation and applies globally across the cluster.

C. RBAC is only applicable to Pods and does not extend to other Kubernetes resources.

D. RBAC uses roles and role bindings to grant permissions to users for specific resources and actions.

A. Implementing a modular architecture with well-defined APIs and interfaces that allows platform capabilities to be independently added, updated, or removed without disrupting the entire system.

B. Designing a platform with centralized configuration management that can quickly implement organization-wide changes through a single control plane operated by platform specialists.

C. Building a monolithic platform with comprehensive documentation that provides complete instructions for users to modify internal components when new capabilities need to be added or removed.

D. Creating a platform with a flexible governance model that requires all capability changes to be reviewed by specialized teams before being approved, ensuring consistent implementation across all platform areas.

A. To publish versioned artifacts that can be tracked and used to inform users of new releases.

B. To enable the registry service to execute automated tests on the uploaded container image.

C. To allow the container image to be analyzed and transformed back into source code.

D. To store the image in a central registry so deployment environments can pull it for release.

A. Employ a GitOps controller to synchronize Git-stored Helm and Crossplane configurations.

B. Integrate Helm and Crossplane into a GitOps-enabled CI/CD pipeline.

C. Leverage Git for configuration storage, with manual application of Helm and Crossplane.

D. Use Helm and Crossplane, with manual GUI-based configuration updates.

A. Lead Time for Changes

B. Mean Time to Recover (MTTR)

C. Service Level Agreements (SLAs)

D. Change Failure Rate

A. Encouraging platform feedback loops from developers to improve usability.

B. Keeping platform development separate from application teams.

C. Mandating that all teams must use the platform without exceptions

D. Prioritizing platform security over usability.

A. Creating separate Git repositories per application.

B. Employing a declarative application deployment definition.

C. Direct deployments from CI/CD with Git configuration.

D. Using Helm for application packaging with manual deployments.

A. Manual infrastructure deployment services.

B. A comprehensive platform knowledge center.

C. Centralized logging and monitoring interfaces.

D. Self-service resource provisioning APIs.