Cloud Native Architecture
medium

Questão de Cloud Native Architecture #019e3a4f

Enunciado da Questão
Cloud Native Architecture
#cloud-native
#devops
#sre
#workload-management
Médio

In a cloud native environment, who is usually responsible for maintaining the workloads running across the different platforms?

A

The cloud provider.

B

The Site Reliability Engineering (SRE) team.

C

The team of developers.

Correta
D

The Support Engineering team (SE).

Explicação Oficial / Explicações da Comunidade

In a cloud native environment, the team of developers is usually responsible for maintaining the workloads running across different platforms. This aligns with the DevOps principle of shared responsibility, where developers own the entire lifecycle of their applications, from development to production.

How it Works

Cloud native architectures emphasize microservices, containers, and orchestration platforms like Kubernetes. The development team builds, deploys, and monitors their services, often using CI/CD pipelines and observability tools. This model reduces handoffs and accelerates issue resolution.

Why the Correct Answer is Right

The team of developers is correct because cloud native practices promote "you build it, you run it." Developers have the deepest knowledge of the code and can quickly diagnose and fix issues. They use tools like Prometheus for monitoring, Helm for packaging, and Kubernetes for orchestration, ensuring workloads are maintained efficiently.

Why the Incorrect Answers are Wrong

  • The cloud provider: Cloud providers manage the underlying infrastructure (compute, storage, networking) but do not maintain customer workloads. Their responsibility ends at the hypervisor or container runtime level.
  • The Site Reliability Engineering (SRE) team: SRE teams focus on reliability, scalability, and automation of infrastructure, but they typically do not own individual application workloads. They provide platforms and best practices, while developers maintain their own services.
  • The Support Engineering team (SE): Support engineers handle user-reported issues and escalations, but they are not responsible for ongoing maintenance of workloads. Their role is reactive, not proactive, and they lack the deep code context needed for workload maintenance.