hardMultiple SelectObjective-mapped
300-410 Practice Question: Which TWO statements about the 'logging buffered'…
Which TWO statements about the 'logging buffered' command and its interaction with other logging commands are correct? (Choose TWO.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The command 'logging buffered 4096' sets the buffer size to 4096 bytes and enables logging to the buffer.
The 'logging buffered' command enables logging to an internal buffer. The size can be specified in bytes. The 'logging console' and 'logging buffered' are independent; disabling one does not affect the other. The 'logging monitor' controls terminal line logging. The 'logging on' command globally enables logging output; without it, no logging occurs. The 'no logging buffered' command disables buffer logging but does not clear the buffer.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The command 'logging buffered 4096' sets the buffer size to 4096 bytes and enables logging to the buffer.
Why this is correct
Correct. This command enables buffered logging with a buffer size of 4096 bytes.
- ✗
Disabling console logging with 'no logging console' also disables buffered logging.
Why it's wrong here
Incorrect. Console logging and buffered logging are independent; disabling one does not affect the other.
- ✓
If 'logging buffered' is configured, the buffer can be viewed using the 'show logging' command.
Why this is correct
Correct. The 'show logging' command displays the contents of the logging buffer.
- ✗
The 'logging buffered' command requires 'logging on' to be configured first; otherwise, it has no effect.
Why it's wrong here
Incorrect. 'logging on' is enabled by default; 'logging buffered' works independently, but if 'logging off' is configured, no logging occurs.
- ✗
The 'no logging buffered' command clears the buffer and stops all logging to the buffer.
Why it's wrong here
Incorrect. 'no logging buffered' disables buffered logging but does not clear the buffer; the buffer retains old messages until overwritten.
Go deeper
Related to this question
About these practice questions
One of 1,966 original 300-410 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on 300-410
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. What is the default behavior of the 'logging buffered' command in Cisco IOS-XE when no severity level is specified?
medium- A.It captures only messages of severity 0 through 4.
- B.It captures only messages of severity 0 through 5.
- C.It captures only messages of severity 0 through 6.
- ✓ D.It captures messages of severity 0 through 7.
Why D: When 'logging buffered' is configured without a severity level, it defaults to severity 7 (debugging), capturing all messages.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 300-410 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 300-410 exam.