Each replica of a public-works work-order API writes its own dated log file under /var/log on the container filesystem. Operators cannot search one incident across replicas after a node is replaced. Which logging design matches cloud-native practice?
Select an answer to reveal the explanation.
Short Explanation
Logs should flow like a radio broadcast the station records—not like sticky notes taped inside each taxi that vanish when the car is retired. Stdout as a stream lets the platform capture and search across replicas. Private per-host files die with the host.
Full Explanation
Cloud-native processes emit a time-ordered event stream on standard output so the platform can collect logs from every replica. Files local to a container or host disappear when that instance is replaced and cannot be queried as one corpus. SCP-after-the-fact, silence in production, and email floods are not workable design rules. OCI Logging product setup belongs in a later domain.