CV0-002 · Question #592
A new corporate security policy mandates that all external user API calls to the PaaS environment must be logged and retained for six months. Immediately after implementing the change on the PaaS…
The correct answer is B. Logging rollover is not configured. After implementing a new security policy to log all external user API calls for six months on a PaaS environment, performance issues arose. The most likely cause is that logging rollover is not configured, which leads to unmanaged log growth and system strain.
Question
A new corporate security policy mandates that all external user API calls to the PaaS environment must be logged and retained for six months. Immediately after implementing the change on the PaaS servers, developers started reporting performance issues. Which of the following is the MOST likely cause of the issues?
Options
- ALogging services are not enabled.
- BLogging rollover is not configured.
- CLogging events are too high.
- DLogging has consumed all storage.
How the community answered
(15 responses)- A7% (1)
- B73% (11)
- C13% (2)
- D7% (1)
Why each option
After implementing a new security policy to log all external user API calls for six months on a PaaS environment, performance issues arose. The most likely cause is that logging rollover is not configured, which leads to unmanaged log growth and system strain.
If logging services were not enabled, no logs would be generated, and therefore, performance issues directly attributable to the logging process would not occur.
Logging rollover mechanisms are essential to manage log file size and age, ensuring that logs are archived, compressed, or deleted after reaching specific thresholds. If not configured, continuous logging, especially over a six-month retention period, will lead to excessive disk I/O, CPU usage, and storage consumption, significantly degrading system performance.
While a high volume of logging events contributes to the problem, the specific cause of performance degradation over time for a high volume of logs is the lack of proper management through a logging rollover configuration.
If logging had consumed all storage, the system would likely encounter critical errors or crash, which is a more severe symptom than general 'performance issues', and logging rollover is the preventive measure against this scenario.
Concept tested: PaaS logging management and performance
Source: https://learn.microsoft.com/azure/azure-monitor/logs/data-retention-costs
Topics
Community Discussion
No community discussion yet for this question.