ACL rules and categories in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new user with read-only access to keys.

Redis

ACL SETUSER readonly_user on >password ~* +[1]

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

Aget

Bset

Cdel

Dconfig

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'set' grants write access, not read-only.

Using 'del' allows deleting keys, which is not read-only.

Using 'config' allows configuration changes, not just reading.

The get command allows read-only access to keys. Using +get grants permission to read data.

2fill in blank

medium

Complete the code to allow a user to execute all commands in the 'string' category.

Redis

ACL SETUSER string_user on >pass123 ~* +@[1]

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

Ahash

Blist

Cstring

Dset

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'hash' grants access to hash commands, not string.

Choosing 'list' or 'set' grants access to other data types.

The string category includes commands that operate on string values. Using +@string grants access to all string commands.

3fill in blank

hard

Fix the error in the ACL command that tries to deny all commands but accidentally allows 'config'.

Redis

ACL SETUSER limited_user on >pass ~* +[1] -@all

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

Adel

Bget

Cset

Dconfig

Attempts:

3 left

💡 Hint

Common Mistakes

Not noticing that '+config' overrides '-@all'.

Confusing allowed commands with denied ones.

The command +config explicitly allows the 'config' command, which contradicts the intention to deny all commands. Removing or not adding +config is needed to deny it.

4fill in blank

hard

Fill both blanks to create a user that can only run commands in the 'list' category and only on keys starting with 'user:'.

Redis

ACL SETUSER list_user on >pass123 ~[1] +@[2]

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

Auser:*

Bstring

Clist

Dhash

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong key pattern that doesn't restrict keys.

Choosing the wrong command category.

The pattern user:* restricts keys to those starting with 'user:'. The category list allows all list commands.

5fill in blank

hard

Fill all three blanks to create a user that can run 'get' and 'set' commands only on keys starting with 'cache:', and cannot run any other commands.

Redis

ACL SETUSER cache_user on >cachepass ~[1] +[2] +[3] -@all

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

Acache:*

Bget

Cset

Ddel

Attempts:

3 left

💡 Hint

Common Mistakes

Not denying all other commands with '-@all'.

Allowing commands not related to 'get' or 'set'.

The key pattern cache:* limits keys to those starting with 'cache:'. Adding +get and +set allows only these commands. The -@all denies all other commands.

Practice

1. What is the main purpose of ACL rules in Redis?

easy

A. To control user access to commands and keys

B. To store data persistently on disk

C. To optimize query performance

D. To backup the database automatically

Solution

1. Step 1: Understand ACL rules function

   ACL rules define what commands and keys a user can access in Redis.

2. Step 2: Compare options with ACL purpose

   Only To control user access to commands and keys matches the control of user access, others describe unrelated features.

3. Final Answer:

   To control user access to commands and keys -> Option A

4. Quick Check:

   ACL rules = control access [OK]

Hint: ACL rules control access permissions in Redis [OK]

Common Mistakes:

• Confusing ACL rules with data storage
• Thinking ACL rules optimize performance
• Mixing ACL with backup features

2. Which of the following is the correct syntax to add a user with ACL rules in Redis?

easy

A. ACL SETUSER alice on >password ~* +@all

B. ACL CREATEUSER alice on >password ~* +@all

C. ACL ADDUSER alice on >password ~* +@all

D. ACL NEWUSER alice on >password ~* +@all

Solution

1. Step 1: Recall Redis ACL command for user creation

   The correct command to create or update a user is ACL SETUSER.

2. Step 2: Check each option's command

   Only ACL SETUSER alice on >password ~* +@all uses ACL SETUSER, others use invalid commands.

3. Final Answer:

   ACL SETUSER alice on >password ~* +@all -> Option A

4. Quick Check:

   Use ACL SETUSER to add/update users [OK]

Hint: Use ACL SETUSER to add or update users [OK]

Common Mistakes:

• Using ACL ADDUSER instead of ACL SETUSER
• Using ACL CREATEUSER or ACL NEWUSER which don't exist
• Confusing command names

3. Given the ACL rule ACL SETUSER bob on >mypassword ~cache:* +@read, which commands can user 'bob' execute?

medium

A. Only write commands on any keys

B. All commands including write commands

C. Only read commands on keys starting with 'cache:'

D. No commands because the user is off

Solution

1. Step 1: Analyze the ACL rule components

   User 'bob' is enabled (on), password set, keys limited to pattern 'cache:*', and allowed commands are in category '@read'.

2. Step 2: Determine allowed commands and keys

   Only read commands (+@read) on keys matching 'cache:*' are allowed.

3. Final Answer:

   Only read commands on keys starting with 'cache:' -> Option C

4. Quick Check:

   ACL keys + command categories limit access [OK]

Hint: Check key pattern and command category for user permissions [OK]

Common Mistakes:

• Assuming all commands are allowed
• Ignoring key pattern restrictions
• Thinking user is disabled

4. You run ACL SETUSER alice on >pass123 ~* +@write but Alice cannot execute SET commands. What is the likely issue?

medium

A. The user is not enabled

B. The command category @write does not include SET

C. The key pattern ~* is too restrictive

D. The password is incorrect

Solution

1. Step 1: Verify user status and rules

   User 'alice' is enabled (on), password set, keys unrestricted (~*), commands allowed in @write category.

2. Step 2: Check if SET is in @write category

   SET command belongs to @string category, not @write, so permission is missing.

3. Final Answer:

   The command category @write does not include SET -> Option B

4. Quick Check:

   Command categories must include needed commands [OK]

Hint: Confirm command category includes the command you want [OK]

Common Mistakes:

• Assuming @write includes all write commands
• Thinking key pattern restricts commands
• Ignoring user enabled status

5. You want to create a Redis user 'cacheAdmin' who can run all commands related to caching and keys starting with 'cache:'. Which ACL rule is correct?

hard

A. ACL SETUSER cacheAdmin on >secret ~cache:* +@read +@write

B. ACL SETUSER cacheAdmin on >secret ~cache:* +@all

C. ACL SETUSER cacheAdmin on >secret ~* +@cache

D. ACL SETUSER cacheAdmin on >secret ~cache:* +@cache +@keyspace

Solution

1. Step 1: Identify key pattern restriction

   User must access keys starting with 'cache:', so pattern ~cache:* is needed.

2. Step 2: Select command categories for caching

   Commands related to caching are in @cache and key management in @keyspace categories.

3. Step 3: Evaluate options

   ACL SETUSER cacheAdmin on >secret ~cache:* +@cache +@keyspace correctly combines key pattern and relevant categories; others either allow too much or wrong keys.

4. Final Answer:

   ACL SETUSER cacheAdmin on >secret ~cache:* +@cache +@keyspace -> Option D

5. Quick Check:

   Use key pattern + relevant categories for precise access [OK]

Hint: Combine key patterns with correct categories for precise ACL [OK]

Common Mistakes:

• Using ~* allows all keys, not just cache keys
• Using +@all grants too many permissions
• Missing key pattern restriction