Which three are features and benefits of Tanzu Kubernetes Grid? (Choose three.)

Question

Options

• AMonitor full-stack applications to cloud infrastructures with metrics, traces, span logs, and
• BExtend the same consistent Kubernetes runtime across your public cloud and edge environments
• CProvide Container Build Services consistently to a fleet of clusters
• DAutomated multicluster operations
• ELocal and in-cluster platform services including logging, monitoring, networking, and storage
• FA continuously maintained catalog of open-source components and applications

Explanation

B, D, and E are the three correct answers, each mapping to a core pillar of Tanzu Kubernetes Grid (TKG).

B is correct because TKG's primary value proposition is delivering a consistent, certified Kubernetes runtime that spans on-premises data centers, public clouds (AWS, Azure), and edge - eliminating environment-specific drift. D is correct because TKG includes automated lifecycle management for fleets of clusters (provisioning, upgrades, scaling) via the Cluster API model. E is correct because TKG bundles in-cluster platform services out of the box - including Contour (ingress/networking), Fluent Bit (logging), Prometheus/Grafana (monitoring), and storage integrations - so operators don't assemble these themselves.

The distractors belong to other Tanzu products: A (metrics, traces, span logs) describes Tanzu Observability (Aria Operations for Applications / Wavefront); C (Container Build Services for a fleet) describes Tanzu Build Service; and F (catalog of open-source components) describes Tanzu Application Catalog (Bitnami).

Memory tip: Think of TKG as the runtime + operations + services layer - "Run it everywhere (B), manage many at once (D), batteries included (E)." The other options each belong to a separate, named Tanzu product.

No community discussion yet for this question.