Q: 5
h company uses shared drives as part of a workforce collaboration process. To ensure the correct access permissions, inheritance at the top-level folder is assigned to each department. A manager's team is working on confidential material and wants to ensure only the immediate team can view a specific folder and its subsequent files and subfolders. Which of the following actions should the technician most likely take?
Options
Discussion
D . Turning off inheritance only on the confidential folder and then setting team permissions is way easier than touching every file. This keeps it scoped and manageable. Pretty sure that's the intent unless each subfolder needs custom access.
Option D official study guide definitely covers this scenario with access inheritance. Pretty sure that's what CompTIA wants here.
D . If you only want that confidential folder and everything under it to be restricted to the team, break inheritance there, set the new permissions, then let all child items inherit those tighter settings. Less work and still keeps the top-level department perms in place elsewhere. Only tricky if subs actually needed custom perms, but here D fits best I think.
For me, D. The question says all files and subs should be locked down for the team, so breaking inheritance just at that folder then letting its children inherit the new tighter permissions makes sense. A is tempting but too manual here.
A is wrong, D. Had something like this in a mock-break inheritance just for that folder, set new team permissions, then let subfolders inherit. Keeps it clean and avoids crazy manual edits. I think that's the intended approach unless every child needs a unique setup.
I don’t think it’s A. D gives the team exclusive access without the painful manual work A requires.
I’m kinda torn, D seems right but could see A if every subfolder needed unique permissions. Just not sure if that’s what the scenario wants. Leaning toward D since it's less manual effort.
D , that's what the official guide and some practice tests highlight. Turning off inheritance at the folder you want, setting tight permissions there, then enabling inheritance for its subfolders is the easiest way to keep things clean and consistent for that team. Pretty sure that's what most CompTIA learning materials show.
Yeah, D makes sense here. You break inheritance just on the confidential folder, apply the team-only permissions there, then let subfolders/files inherit that restriction. Much less manual permission work than A. Pretty sure that's what CompTIA’s looking for, unless you need every file locked down differently. Agree?
Ugh, CompTIA always makes the permissions thing way messier than real life. I’d say A since you could just set each file manually after breaking inheritance, which gives total control you know? But maybe I’m missing a trick.
Be respectful. No spam.
