Exam 350-901 topic 1 question 154 discussion

Correct answers: A & E Centralized logging has nothing to do with reduced CPU and memory. A. reduces the time required to query log data across multiple hosts - it is better to search in a single place than multiple to find a root cause - Correct B. reduces the loss of logs after a single disk failure - It will reduce the data loss if the disk belongs to the application, but this could be a problem if the disk belongs to the centralized logging and how the logging has been deployed (multiples disks maybe?) E. provides compression and layout of log data - The compression could be done depending on the tools and storage that you will use. Also, a layout will be provided. - Correct

A, B are correct.

Why Not the Other Options? C (Improves application performance by reducing CPU usage) ❌ Centralized logging focuses on log aggregation and storage, not directly on application CPU performance. D (Improves application performance by reducing memory usage) ❌ While centralized logging reduces the burden of log storage and management on individual hosts, it does not have a significant impact on an application's memory usage. E (Provides compression and layout of log data) ❌ While some centralized logging services might offer compression, this is not a core benefit or purpose of centralized logging.

I'll go with A & B.

A and E seem the best answers here. A. reduces the time required to query log data across multiple hosts - it is better to search in a single place than multiple to find a root cause - Correct B. reduces the loss of logs after a single disk failure - It will reduce the data loss if the disk belongs to the application, but this could be a problem if the disk belongs to the centralized logging and how the logging has been deployed (multiples disks maybe?) - I'm not sure about this. C. improves application performance by reducing CPU usage - It will improve the CPU of the application, but the centralized logging will consume more CPU per application since we can specify that the log will be processed by the logging instead of being processed locally. In network devices, we can spread which logs will be processed locally and which ones will not. I'm not sure if this could be easily applied to the code as well. D. improves application performance by reducing memory usage - The same idea of CPU usage - I'm not either. E. provides compression and layout of log data - The compression could be done depending on the tools and storage that you will use. Also, a layout will be provided. - Correct

A and E for me. If the central logging server has one disk, then it will still fail. That is why B is IMO incorrect.

A&E looks right. B doesn't sound correct, at least not without knowing how that "centralized" logging server is set-up (physically and logically). There's no clue to know if it has a single Disk, or Disk redundancy (although one could make the case that it would be very unlikely to set up a centralized log server without HD redundancy of some sort).

B doesn't make sense. Because also a logserver can fail and loss data. So A&E make most sense.

IMO this should be A & E.

A and B are correct as from official Study guide page 112: "Logs become distributed as well, and now it's unfeasible to connect to each component...The solution to this problem is to send all the generated logs to an external, centralized place...where all the logs are easily found."

A and E

IMO A and C are corect.