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

Questions 21–25

1. 21foundation · easy

   What type of information is considered contextual data that should be included in log entries to aid in correlation?

   • AThe server's CPU temperature
   • BThe exact memory address of the log statement
   • CThe developer's name who wrote the code
   • DThe user ID, session ID, and request ID
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A company must retain logs for 3 years for compliance, but their log management platform charges significantly more for hot storage than cold storage. The operations team needs to access logs from the last 90 days for active troubleshooting. They also need to ensure that logs containing personal data are protected throughout the retention period. Which strategy best balances cost, access, and compliance?

   • AKeep all logs in hot storage for 3 years to ensure instant access and apply encryption only to the hot tier.
   • BKeep logs in hot storage for 90 days, then transition to cold storage for the remaining 2 years and 9 months, with encryption and access controls applied at both tiers.
   • CStore logs in cold storage from day one to minimize cost, and accept slower access for recent troubleshooting.
   • DDelete logs after 90 days to avoid storage costs and rely on the application's database backups for compliance.
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   Which log level is most appropriate for logging a condition that indicates a potential problem but does not prevent the application from continuing to function?

   • ADEBUG
   • BINFO
   • CERROR
   • DWARN
   Reveal Solution Discussion Select an answer first
5. 24application · medium

   A startup is building a new application and wants to establish a logging strategy from day one. They have a small team and limited budget. They expect the application to grow and be deployed across multiple servers. Which approach best balances simplicity, cost, and future scalability?

   • ASend logs directly to a shared network drive using a common file path for all servers.
   • BLog only ERROR-level messages to a single file on the primary server and ignore all other levels.
   • CWrite logs to local files on each server and have developers SSH in to inspect them when needed.
   • DUse a centralized log aggregation service that collects logs from all servers via a lightweight agent, with structured JSON output.
   Reveal Solution Discussion Select an answer first
6. 25expert · hard

   A team is designing a logging pipeline for a global application. They must comply with data residency regulations that require personal data to stay within specific geographic regions. They use a central log aggregation service in a single region. Which approach should they take to comply with data residency while maintaining a unified view?

   • AMask all personal data in logs before sending them to the central service, so no personal data leaves the region.
   • BSend all logs to the central aggregation service and rely on encryption to satisfy data residency requirements.
   • CDeploy regional log aggregation instances that store logs locally, and configure the central dashboard to query each regional instance without copying the data.
   • DStore logs only on the application servers in each region and do not aggregate them centrally.
   Reveal Solution Discussion Select an answer first