A.  

SBOM generation and security scanning are particularly valuable for application software. While platform software may have different security considerations, these practices are highly beneficial within CI/CD pipelines for applications.

B.  

CI/CD pipelines should integrate SBOM generation and security scanning as automated steps within the build and test phases to ensure early detection of vulnerabilities and maintain a clear inventory of components.

C.  

CI/CD pipelines are designed to accelerate the delivery of platform software, and adding SBOM generation and security scanning would slow down the process, so these activities are better suited for periodic audits conducted outside of the pipeline.

D.  

CI/CD pipelines are primarily for automating deployments; SBOM generation and security scanning are separate, manual processes performed after deployment.

A.  

Manual service dependencies configuration within application code.

B.  

Shared service connection strings and network configurations document.

C.  

Direct Kubernetes API access with detailed documentation.

D.  

Service catalog with abstracted APIs and automated service registration.

A.  

Customer involvement should be limited during the development process to avoid disruptions.

B.  

Teams should continuously gather feedback and iterate on their work to improve outcomes.

C.  

Teams should strictly adhere to initial project plans without making adjustments during development.

D.  

Development and operations teams should remain separate to maintain clear responsibilities.

A.  

Isolates different stages of application development and deployment

B.  

Reduces cloud costs by running applications in different locations.

C.  

Increases application performance by distributing traffic.

D.  

Ensures all applications use the same infrastructure.

A.  

Encrypts the sensitive data stored in etcd.

B.  

Protects workloads against threats during execution.

C.  

Scans container images before deployment.

D.  

Manages the access control to the Kubernetes API.

A.  

HEART evaluates Hardware, Efficiency, Availability, Response times, and Throughput to measure and ensure platform reliability and performance.

B.  

HEART tracks Happiness, Engagement, Adoption, Reliability, and Throughput, helping teams optimize infrastructure performance.

C.  

HEART focuses on Happiness, Engagement, Adoption, Retention, and Task success, enabling teams to track both qualitative and quantitative metrics for user experience.

D.  

HEART focuses on Happiness, Efficiency, Availability, Reliability, and Throughput, enabling teams to assess both qualitative and quantitative aspects of platform performance.

A.  

Declarative

B.  

Imperative

C.  

Hybrid

D.  

Manual

A.  

Integrate AI/ML steps into standard developer CI/CD systems for maximum reuse

B.  

Implement strict resource quotas and isolation for AI/ML workloads for stability.

C.  

Offer workflows and easy access to specialized AI/ML tools, data, and compute.

D.  

Focus the portal on UI-driven execution of predefined AI/ML jobs via abstraction.

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.  

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

B.  

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

C.  

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

D.  

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

A.  

Manual infrastructure deployment services.

B.  

A comprehensive platform knowledge center.

C.  

Centralized logging and monitoring interfaces.

D.  

Self-service resource provisioning APIs.

A.  

It requires all clusters to have the exact same configuration, including secrets and environment variables, to maintain uniformity.

B.  

It ensures consistent and auditable management of configurations and policies across clusters from a single Git repository or set of coordinated repositories.

C.  

It eliminates the need for automated deployment tools like Argo CD or Flux since configurations are already stored centrally.

D.  

It makes it impossible for different teams to customize configurations for specific clusters, reducing flexibility.

A.  

Mandating that all teams must use the platform without exceptions

B.  

Keeping platform development separate from application teams.

C.  

Prioritizing platform security over usability.

D.  

Encouraging platform feedback loops from developers to improve usability.

A.  

Lead Time for Changes

B.  

Mean Time to Recover (MTTR)

C.  

Change Failure Rate

D.  

Service Level Agreements (SLAs)

A.  

Use GitOps to manage RBAC roles and allow teams to request access via pull requests with automatic approval for non-sensitive environments.

B.  

Dedicate one Cloud Native Platform Engineer to triage and fulfill all access requests to maintain fast turnaround times.

C.  

Set up scheduled access windows and batch all requests into specific time slots managed by the platform team.

D.  

Provide pre-approved kubeconfigs to trusted developers so they can access staging clusters without platform intervention.

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.

A.  

The organizational practice of assigning unique pipeline configurations based on application priority levels.

B.  

The technical differences in build tools, testing frameworks, and artifact formats across programming languages.

C.  

The need to accommodate varying team sizes and developer expertise levels within the organization.

D.  

The requirement to visually distinguish between different application pipelines in monitoring dashboards.

A.  

Automatically generate detailed incident documentation, including the timeline and actions taken by the response team.

B.  

Centralize alerts, facilitate notification to the appropriate on-call personnel, coordinate communication, and provide visibility into the incident status.

C.  

Retroactively analyze system logs and metrics after the incident resolution to identify the root cause.

D.  

Automatically execute predefined remediation scripts on the affected systems to resolve the incident without human intervention.

A.  

Simplifying platform management by using identical resource settings everywhere.

B.  

Encouraging developers to maximize resource usage in all environments for stress testing.

C.  

Enforcing strict resource parity, ensuring development environments constantly mirror production exactly.

D.  

Aligning resource allocation with the specific purpose and constraints of each environment.

A.  

Grafana

B.  

ELK Stack

C.  

OpenTelemetry

D.  

Prometheus

A.  

CI/CD is predominantly a pull model, with the container image providing the desired state.

B.  

GitOps is predominantly a push model, with an operator reflecting the desired state.

C.  

GitOps is predominantly a pull model, with a controller reconciling desired state.

D.  

CI/CD is predominantly a push model, with the user providing the desired state.

A.  

The syncer continuously checks the git repository for changes and applies them to the target cluster.

B.  

The target cluster sends updates to the git repository whenever a change is made.

C.  

The syncer uses webhooks to notify the target cluster of changes in the git repository.

D.  

The git repository pushes configuration changes directly to the syncer without any checks.

A.  

CI/CD pipeline

B.  

Service mesh

C.  

Service bus

D.  

Observability pipeline

A.  

Providing a documented process for developers to submit feature requests for the platform.

B.  

Developing a dashboard that visualizes platform usage statistics without exposing any APIs.

C.  

Allowing developers to request and manage development environments on demand through an internal tool.

D.  

Implementing a CI/CD pipeline that automatically deploys updates to the platform based on developer requests.

A.  

User Interface

B.  

Networking

C.  

Traces

D.  

Databases