What is a significant challenge when configuring PowerProtect Data Manager for Kubernetes cluster backup?

Question

Options

• AManaging cluster node backups
• BBalancing resource allocation
• CBackup of ephemeral data
• DNetwork configuration for inter-cluster communication

• A
  7% (3)
• B
  2% (1)
• C
  82% (36)
• D
  9% (4)

Explanation

Backing up ephemeral data (C) is the core challenge because Kubernetes workloads are designed around transient, short-lived containers and volumes - data that exists only for the lifetime of a pod. PowerProtect Data Manager must distinguish between persistent volumes worth protecting and ephemeral storage that disappears when pods terminate, making consistent, meaningful backups difficult to scope and orchestrate.

Why the distractors are wrong:

• A (cluster node backups): Node-level backup is straightforward and not specific to Kubernetes' complexity; PPDM focuses on application-consistent workload protection, not raw node images.
• B (resource allocation): While resource balancing is a general Kubernetes concern, it is not a backup-specific configuration challenge for PPDM.
• D (inter-cluster network config): Network communication between clusters is an infrastructure/CNI concern, not a distinctive challenge introduced by configuring PPDM for backup.

Memory tip: Think "Kubernetes = cattle, not pets" - workloads are meant to be disposable, so the hard part is knowing what to save before it's gone. Ephemeral = exam answer.

No community discussion yet for this question.