CCAAK · Question #16
You use Kafka to process financial transactions in real time. All clients that interact with Kafka must set a descriptive 'clientID', use 'acks=all', and enable compression. A review of the Kafka…
The correct answer is C. Set the 'request.logger' to DEBUG to reveal the 'clientID' in the 'kafka-request.log'. Enabling DEBUG level for the request logger provides detailed request information, including the client identifier, allowing you to trace which client on the shared platform is generating the failed authentication requests.
Question
You use Kafka to process financial transactions in real time. All clients that interact with Kafka must set a descriptive 'clientID', use 'acks=all', and enable compression. A review of the Kafka broker logs reveals a large number of failed authentication requests coming from a specific IP address. This IP address is associated with a shared hardware platform hosting many applications. You need to associate a client with the IP address making the failed authentication requests. How can you find the client making the failed authentication requests?
Options
- ASet the 'request.logger' to INFO to reveal the 'clientID' in the 'kafka-request.log'.
- BSearch for the 'clientID' in the 'kafka-authorizer.log' to reveal the identity of the application.
- CSet the 'request.logger' to DEBUG to reveal the 'clientID' in the 'kafka-request.log'.
- DSet the 'request.logger' to WARN to reveal the 'clientID' of the application.
How the community answered
(22 responses)- A9% (2)
- B14% (3)
- C73% (16)
- D5% (1)
Explanation
Enabling DEBUG level for the request logger provides detailed request information, including the client identifier, allowing you to trace which client on the shared platform is generating the failed authentication requests.
Topics
Community Discussion
No community discussion yet for this question.