Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

F5 Networks Exam 301b Topic 8 Question 91 Discussion

Actual exam question for F5 Networks's 301b exam
Question #: 91
Topic #: 8
[All 301b Questions]

An LTM Specialist needs to modify the logging level for tcpdump execution events. Checking the BigDB Key, the following is currently configured:

sys db log.tcpdump.level {

value "Notice"

}

Which command should the LTM Specialist execute on the LTM device to change the logging level to informational?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Jannette
1 months ago
I'm going with A. It's the most straightforward way to update the logging level. Plus, I heard the 'tmsh set' command is the developer's secret handshake.
upvoted 0 times
Chantay
1 days ago
I agree, it's the most straightforward way to make the change.
upvoted 0 times
...
Kenny
3 days ago
That's correct! 'tmsh set' is the right command to update the logging level.
upvoted 0 times
...
Vince
5 days ago
A) tmsh set /sys db log.tcpdump.level value informational
upvoted 0 times
...
...
Kaitlyn
2 months ago
D is not the right answer. 'status' is not a valid parameter for the 'log.tcpdump.level' key.
upvoted 0 times
Peggie
7 days ago
C) tmsh modify /sys db log.tcpdump.level value informational
upvoted 0 times
...
Kanisha
14 days ago
B) tmsh set /sys db log.tcpdump.level status informational
upvoted 0 times
...
Joesph
24 days ago
A) tmsh set /sys db log.tcpdump.level value informational
upvoted 0 times
...
...
Darci
2 months ago
C looks good to me. 'tmsh modify' is the command we use to update existing BigDB keys, so that makes sense.
upvoted 0 times
Noelia
15 days ago
D) tmsh modify /sys db log.tcpdump.level status informational
upvoted 0 times
...
Luis
28 days ago
C) tmsh modify /sys db log.tcpdump.level value informational
upvoted 0 times
...
Ria
1 months ago
B) tmsh set /sys db log.tcpdump.level status informational
upvoted 0 times
...
Portia
2 months ago
A) tmsh set /sys db log.tcpdump.level value informational
upvoted 0 times
...
...
Veronika
2 months ago
I think B is the way to go. 'status' seems more intuitive than 'value' for changing the logging level.
upvoted 0 times
Sylvia
1 months ago
B) tmsh set /sys db log.tcpdump.level status informational
upvoted 0 times
...
Angella
1 months ago
A) tmsh set /sys db log.tcpdump.level value informational
upvoted 0 times
...
...
Trina
2 months ago
I'm not sure, but I think option A) is the correct command to change the logging level.
upvoted 0 times
...
Vincenza
2 months ago
I agree with Gearldine. Changing the value to informational makes sense for modifying the logging level.
upvoted 0 times
...
Gearldine
2 months ago
I think the answer is A) tmsh set /sys db log.tcpdump.level value informational.
upvoted 0 times
...
Ora
2 months ago
The correct answer is A. The 'tmsh set' command allows you to change the value of a BigDB key, and 'log.tcpdump.level' is the key you need to modify.
upvoted 0 times
Pansy
1 months ago
Thanks for clarifying, I'll remember to use 'tmsh set' for changing logging levels in the future.
upvoted 0 times
...
Dianne
2 months ago
I agree, 'tmsh set' is the right command to modify the logging level for tcpdump execution events.
upvoted 0 times
...
Rueben
2 months ago
That makes sense, using 'tmsh set' is the correct way to change the value of a BigDB key.
upvoted 0 times
...
Tess
2 months ago
A) tmsh set /sys db log.tcpdump.level value informational
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77