Bird
Raised Fist0
Operating Systemsknowledge~20 mins

Access Control Lists (ACLs) in Operating Systems - Practice Problems & Coding Challenges

Choose your learning style10 modes available
Challenge - 5 Problems
🎖️
ACL Mastery Badge
Get all challenges correct to earn this badge!
Test your skills under time pressure!
🧠 Conceptual
intermediate
2:00remaining
Understanding the Purpose of ACLs

What is the primary purpose of Access Control Lists (ACLs) in operating systems?

ATo manage network traffic between devices
BTo encrypt files to prevent unauthorized reading
CTo monitor system performance and resource usage
DTo define which users or groups have permission to access specific files or resources
Attempts:
2 left
💡 Hint

Think about how systems control who can open or modify files.

📋 Factual
intermediate
2:00remaining
ACL Entry Components

Which of the following components is not typically part of an ACL entry?

ATimestamp of last access
BAccess permissions (e.g., read, write, execute)
CUser or group identifier
DType of access (allow or deny)
Attempts:
2 left
💡 Hint

Consider what information controls access versus what is metadata.

🔍 Analysis
advanced
2:00remaining
Effect of Conflicting ACL Entries

Consider a file with the following ACL entries:

  • User Alice: allow read, write
  • User Alice: deny write

What will be Alice's effective permissions on this file?

ARead and write access
BRead access only
CWrite access only
DNo access
Attempts:
2 left
💡 Hint

Think about how deny entries usually override allow entries.

❓ Comparison
advanced
2:00remaining
ACLs vs Traditional Unix Permissions

Which of the following is a key advantage of ACLs over traditional Unix file permissions?

AACLs allow permissions to be set for multiple users and groups beyond owner, group, and others
BACLs automatically encrypt files for security
CACLs replace the need for user authentication
DACLs improve file system performance by caching permissions
Attempts:
2 left
💡 Hint

Think about flexibility in specifying who can access files.

❓ Reasoning
expert
2:00remaining
Security Implications of Misconfigured ACLs

If an administrator accidentally sets an ACL entry that grants 'allow all' permissions to 'everyone' on a sensitive file, what is the most likely consequence?

AThe system will automatically revoke the incorrect ACL entry
BThe file becomes inaccessible to all users including the owner
CUnauthorized users can access and modify the sensitive file
DOnly users in the owner's group can access the file
Attempts:
2 left
💡 Hint

Consider what 'allow all' means for access control.

Practice

(1/5)
1. What is the main purpose of an Access Control List (ACL) in operating systems?
easy
A. To monitor network traffic
B. To store the content of a file securely
C. To manage system hardware devices
D. To specify which users or groups have permissions on a file or resource

Solution

  1. Step 1: Understand what ACLs control

    ACLs list permissions for users or groups on files or resources.
  2. Step 2: Identify the main function

    The main function is to specify who can do what on a resource.
  3. Final Answer:

    To specify which users or groups have permissions on a file or resource -> Option D
  4. Quick Check:

    ACL = user/group permissions [OK]
Hint: ACLs control user permissions on files/resources [OK]
Common Mistakes:
  • Confusing ACL with file content storage
  • Thinking ACL manages hardware
  • Assuming ACL monitors network
2. Which of the following is the correct way to represent an ACL entry for a user named 'alice' with read and write permissions?
easy
A. user:alice:rwx
B. user:alice:rw
C. group:alice:rw
D. user:alice:r

Solution

  1. Step 1: Identify the correct ACL entry format

    ACL entries usually specify type (user/group), name, and permissions.
  2. Step 2: Match permissions to read and write only

    Read and write permissions are 'rw', execute is 'x'. So 'rw' matches read and write.
  3. Final Answer:

    user:alice:rw -> Option B
  4. Quick Check:

    user + alice + rw = correct ACL entry [OK]
Hint: User entries start with 'user:' and list exact permissions [OK]
Common Mistakes:
  • Using 'group' instead of 'user' for a user entry
  • Adding execute permission when not needed
  • Listing only read permission when write is required
3. Given the following ACL entries on a file:
user:alice:rwx
group:staff:r-x
other::r--
What permissions does a user named 'bob' who belongs to the 'staff' group have?
medium
A. Read and execute only
B. Read, write, and execute
C. Read only
D. No permissions

Solution

  1. Step 1: Identify bob's group membership

    Bob belongs to the 'staff' group, so group permissions apply.
  2. Step 2: Check group permissions in ACL

    Group 'staff' has 'r-x' which means read and execute, no write.
  3. Final Answer:

    Read and execute only -> Option A
  4. Quick Check:

    Group 'staff' = r-x = read + execute [OK]
Hint: User's group permissions apply if user not listed explicitly [OK]
Common Mistakes:
  • Assuming user permissions apply to bob
  • Including write permission incorrectly
  • Using 'other' permissions instead of group
4. A system administrator sets an ACL entry as user:bob:r but Bob reports he cannot write to the file. What is the most likely cause?
medium
A. The file is owned by another user
B. Bob is not listed in the ACL
C. The ACL entry only grants read permission, not write
D. The ACL entry syntax is incorrect

Solution

  1. Step 1: Analyze the ACL entry permissions

    The entry 'user:bob:r' grants only read permission, no write.
  2. Step 2: Understand why Bob cannot write

    Without write permission, Bob cannot modify the file.
  3. Final Answer:

    The ACL entry only grants read permission, not write -> Option C
  4. Quick Check:

    Read-only permission blocks writing [OK]
Hint: Check if write permission 'w' is included in ACL entry [OK]
Common Mistakes:
  • Assuming ownership affects ACL permissions directly
  • Thinking syntax error causes permission denial
  • Ignoring the actual permissions granted
5. You want to allow a group named 'developers' to have read and write access to a file, but no execute permission. Which ACL entry correctly achieves this without affecting other permissions?
hard
A. group:developers:rw-
B. group:developers:rwx
C. user:developers:rw-
D. group:developers:r--

Solution

  1. Step 1: Identify the correct ACL entry type

    Since 'developers' is a group, the entry must start with 'group:developers'.
  2. Step 2: Set permissions to read and write only

    Read and write permissions are 'rw-', where '-' means no execute.
  3. Step 3: Confirm no execute permission is given

    group:developers:rw- uses 'rw-' which excludes execute permission.
  4. Final Answer:

    group:developers:rw- -> Option A
  5. Quick Check:

    Group + rw- = read/write, no execute [OK]
Hint: Use 'group:name:rw-' for read/write without execute [OK]
Common Mistakes:
  • Using 'user' instead of 'group' for group permissions
  • Including execute permission by mistake
  • Setting only read permission when write is needed
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard