Q: 4
A Linux administrator is trying to remove the ACL from the file /home/user/dat
a. txt but receives the following error message:
Given the following analysis:
Which of the following is causing the error message?
Options
Discussion
D . Had something like this in a mock, and it was the file attributes (immutable bit) that blocked ACL changes, not SELinux or permissions. Seen this trip people up if they miss the 'lsattr' output.
D. Seen this in similar practice exams, official study guide covers immutable attribute blocking changes too.
Had something like this in a mock, and the immutable flag (file attributes) blocked changes. D matches that scenario, since you have to clear the 'i' bit before modifying ACLs. Pretty confident here but ping if someone disagrees.
D
Seen similar in practice questions, file attributes like immutable can block modification even as root. You need to clear the 'i' bit with chattr first before messing with ACLs. Official guide covers this in the files/directories section. Not 100% but pretty sure D fits here. Anyone else check this against labs?
Seen similar in practice questions, file attributes like immutable can block modification even as root. You need to clear the 'i' bit with chattr first before messing with ACLs. Official guide covers this in the files/directories section. Not 100% but pretty sure D fits here. Anyone else check this against labs?
D imo. It's almost always the immutable attribute with this type of error, not SELinux or mount options. Open to corrections.
D , SELinux (C) catches folks off guard but only D fits with the immutable attribute thing.
Its D, those file attributes like immutable will stop any change even as root.
Honestly, it's not SELinux in this scenario, so D. Easy trap if you miss the immutable attribute part, which always stops file changes like ACL mods even for root. Seen this come up on practice sets.
Makes sense, it's D. That immutable attribute blocks any changes including ACL removal for sure.
C vs D. I was thinking SELinux (C) might explain ACL issues on some systems, especially if enforcing mode is on, but the immutable attribute trap makes D more likely. Wouldn't totally rule out C though.
Be respectful. No spam.
