Describe an Effective Logging Strategy for an Application 350-901 Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   Which of the following is an example of a structured log entry?

   • A2023-10-01 12:00:00 ERROR login failed
   • B"User login failed for user jdoe from IP 10.0.0.1"
   • Clogin_failed|jdoe|10.0.0.1
   • D{"event": "login_failed", "user": "jdoe", "ip": "10.0.0.1"}
   Reveal Solution Discussion Select an answer first
2. 12expert · hard

   A development team is reviewing their logging practices. They currently log all user input validation failures at ERROR level, and they have an alert that triggers on any ERROR log. This has caused alert fatigue, and the team has started ignoring alerts. They want to reduce noise while ensuring real failures are still caught. Which change should they make?

   • ARemove the alert on ERROR logs and rely on manual log review by the on-call engineer.
   • BIncrease the alert threshold to 50 ERROR logs per minute so that occasional validation failures do not trigger alerts.
   • CChange the log level of validation failures to DEBUG so they are not included in the ERROR alert.
   • DReclassify validation failures to WARN and keep the ERROR alert for genuine system failures.
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A DevOps team maintains a microservices-based payment platform. During an incident, they need to trace a single customer transaction across the API gateway, three backend services, and the database. The current logs are plain text with timestamps and messages. The team wants to improve correlation without changing the logging framework. Which approach should they use?

   • ARemove timestamps from logs to reduce noise, and rely on the sequence of messages to reconstruct the transaction flow.
   • BCentralize all logs into a single file on the API gateway host so that entries from all services appear in chronological order.
   • CAdd a unique transaction ID to each log entry as a key-value pair, and propagate it across service calls via HTTP headers.
   • DIncrease the log verbosity to DEBUG level for all services so that every internal step is recorded for manual tracing.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A team runs a distributed system with multiple services. They want to trace a user request as it flows through the system. They have implemented structured logging with JSON. However, when they search for a specific request, they find entries from different services but cannot easily group them. What is the most likely missing piece?

   • AA unique request ID that is generated at the entry point and passed to all downstream services in the call chain.
   • BA centralized log storage that combines all service logs into a single index.
   • CA longer retention period so that all logs from the request are available for search.
   • DA higher log level such as DEBUG to capture more internal details from each service.
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   Which of the following is a key component of an effective logging strategy?

   • ADefining what to log, at what level, and for how long to retain logs
   • BStoring logs only in the application's local file system
   • CLogging every variable value at every line of code
   • DEnsuring logs are only accessible to the application developer
   Reveal Solution Discussion Select an answer first