MENU
After running the command umount /mnt, the following error message is displayed: umount: /mnt: device is busy. What is a common reason for this message?
Suggested Answer: B
Get Premium LCP-001 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
KR
Krissy
12 months ago
Nah, I don't think the rm command would cause that error.
BE
Bev
12 months ago
I think it's also possible that disk writes are still flushing.
DO
Dominga
12 months ago
Wait, how can the kernel think a process is about to open a file? Sounds weird.
SH
Sherron
1 year ago
Totally agree, that's the most likely issue!
RO
Rosamond
1 year ago
Common reason is usually a user has a file open in /mnt.
FE
Fernanda
1 year ago
I feel like the rm command being incomplete could be a possibility, but I don’t recall it being a common reason.
MA
Marylin
1 year ago
I practiced a similar question where a process was holding onto a file, so option E sounds familiar.
IV
Ivette
1 year ago
I’m not entirely sure, but I think the kernel flushing writes could be a reason too, like option A?
TY
Ty
1 year ago
I remember something about files being open in the mounted directory causing issues, so maybe option B is correct?
RO
Roy
1 year ago
Hmm, this one seems straightforward. I think the answer is TLS, since that's the standard protocol for secure syslog transmission.
FR
Francesco
1 year ago
The degree of a table is the number of attributes or fields it contains. Counting the columns in the image, I see there are 4, so the answer is C.
LO
Louann
1 year ago
Okay, I've got this. The key is to monitor all traffic from the Internet and Suspicious IPs that's destined for AWS databases. Option D looks like it covers that.