Integrating Logging, Monitoring, and Alerting DSE Practice Questions (Page 5)

Questions 21–25

1. 21expert · medium

   A DevSecOps team has a mature monitoring pipeline. They want to use the data to drive continuous improvement of their security posture. They have identified that a common vulnerability is introduced during code changes. What is the most effective way to close the feedback loop?

   • ASet up an alert that notifies the security team when the vulnerability is detected in production.
   • BConduct a weekly manual code review to look for the vulnerability.
   • CCreate a dashboard that shows the number of vulnerabilities over time.
   • DAdd a security scanning step to the CI pipeline that checks for the vulnerability pattern and fails the build if found.
   Reveal Solution Discussion Select an answer first
2. 22expert · medium

   A company is subject to data protection regulations that require them to monitor access to sensitive data. They have a mix of on-premises and cloud systems. They need to detect unauthorized access attempts and alert the security team. What is the most important consideration when designing their logging and alerting?

   • AEnsure that all systems log access events in a consistent format and forward them to a central system that can correlate and alert.
   • BUse a different logging tool for each system to avoid vendor lock-in.
   • CLog only successful access events to reduce noise.
   • DStore logs locally on each system and have administrators review them periodically.
   Reveal Solution Discussion Select an answer first
4. 23expert · hard

   A team is building a monitoring system for a critical web application. They have a limited budget and need to choose between investing in distributed tracing or expanding their log aggregation and alerting. The application is a monolithic service with occasional performance issues, and the team's main concern is detecting failures quickly. Which choice is most appropriate?

   • AInvest in distributed tracing because it provides the most detailed visibility.
   • BInvest equally in both tracing and log aggregation to be safe.
   • CUse only infrastructure monitoring and no application-level logging.
   • DExpand log aggregation and alerting because the monolith's performance issues can be detected with logs and metrics.
   Reveal Solution Discussion Select an answer first
5. 24application · medium

   A development team is adding logging to a new service. They want to ensure that logs are useful for both debugging and security analysis. What should they include in their logging strategy?

   • AUse structured logging with consistent fields for event type, timestamp, user ID, and outcome, and avoid logging sensitive values.
   • BLog at the most verbose level in production to capture every detail.
   • CLog only error messages and exceptions, to minimize storage costs.
   • DLog all input data, including passwords and credit card numbers, to aid in debugging.
   Reveal Solution Discussion Select an answer first
6. 25application · medium

   A DevOps team is building a dashboard to monitor a new payment service. They need to detect when the service is slow to respond, identify which downstream database queries are slow, and understand the root cause of a specific failed transaction. Which combination of observability signals should they use?

   • AMetrics for CPU and memory usage, and logs for all application output.
   • BMetrics for latency, traces for request paths and database query times, and logs for detailed error messages.
   • CTraces for all requests, and a dashboard showing trace counts per service.
   • DLogs for every event, and a full-text search engine to query them.
   Reveal Solution Discussion Select an answer first