The correct option is Deploy a log collector such as Fluent Bit or Fluentd to forward application logs to a centralized log store.

Choosing Deploy a log collector such as Fluent Bit or Fluentd to forward application logs to a centralized log store gives you a consistent, resilient pipeline that fits cloud native patterns. Collectors are typically deployed as DaemonSets so they run on every node and capture container stdout and stderr without changing application code. They can parse and enrich structured logs, buffer and retry on network failures, and forward to many backends for search and analysis.

Centralizing logs with this approach makes it easier to correlate traces and metrics and to apply uniform retention and access controls. It also supports multi-cluster and hybrid environments since the collectors act as a standard ingestion layer that can forward to Elasticsearch, Loki, managed logging services, or other destinations.

Capture request and response logs at the API gateway and forward them to a central store is not sufficient because gateway logs only show ingress requests and responses. That option misses internal service logs and background processing, and it cannot replace full application level logging for troubleshooting.

Write logs from each microservice directly to a shared persistent volume mounted across pods is incorrect because shared volumes do not work reliably as a distributed logging bus. Shared volumes introduce concurrency, performance, and portability problems and they break the principle of immutable, ephemeral containers.

Use the native logging service offered by each cloud provider where workloads run is not the best single solution because it fragments your pipeline across vendors. Using provider native services can lead to vendor lock in and inconsistent features across environments, and it does not provide a single, portable collection layer for multi-cloud or hybrid deployments.

Full AWS Practitioner Certification Question