Access Control Lists (ACLs) in Operating Systems - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify what ACL stands for.

Operating Systems

ACL stands for [1].

Drag options to blanks, or click blank then click option'

AAccess Control List

BAutomatic Control Link

CAccess Command Line

DActive Control Layer

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing ACL with command line or network terms.

Thinking ACL is a software or hardware component.

ACL means Access Control List, which is a way to define who can access what on a system.

2fill in blank

medium

Complete the sentence to explain what ACLs do.

Operating Systems

ACLs are used to [1] access to files or resources.

Drag options to blanks, or click blank then click option'

Aignore

Bcontrol

Cdelete

Dcopy

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'ignore' because it sounds like skipping.

Confusing control with copying or deleting.

ACLs control who can read, write, or execute files or resources.

3fill in blank

hard

Fix the error in the statement about ACLs.

Operating Systems

An ACL only allows one user to access a file at a time, so it [1] multi-user access.

Drag options to blanks, or click blank then click option'

Ablocks

Bignores

Callows

Dcreates

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking ACLs block multi-user access.

Confusing ACLs with file locking mechanisms.

ACLs allow multiple users to have different permissions on the same file.

4fill in blank

hard

Fill both blanks to complete the ACL entry example.

Operating Systems

user:[1]:[2]

Drag options to blanks, or click blank then click option'

Aalice

Bread

Cwrite

Dbob

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping username and permission.

Using a username that is not in the options.

This ACL entry means user 'alice' has 'read' permission.

5fill in blank

hard

Fill all three blanks to create a valid ACL rule.

Operating Systems

[1]:[2]:[3]

Drag options to blanks, or click blank then click option'

Agroup

Bdevelopers

Cexecute

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up 'user' and 'group' in the first blank.

Choosing a permission not listed in options.

This ACL rule means user 'developers' has 'execute' permission.

Practice

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