Creating users and roles in MongoDB - Performance & Efficiency

Time Complexity: Creating users and roles

O(log n)

Understanding Time Complexity

When we create users and roles in MongoDB, we want to know how the time it takes changes as we add more users or roles.

We ask: How does the work grow when the number of users or roles grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    db.createUser({
      user: "alice",
      pwd: "password123",
      roles: [ { role: "readWrite", db: "sales" } ]
    });

    db.createRole({
      role: "reporter",
      privileges: [ { resource: { db: "sales", collection: "reports" }, actions: [ "find" ] } ],
      roles: []
    });
    

This code creates one user and one role with specific permissions in the database.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Indexed lookup to check existing users and roles to ensure no duplicates before creation.
• How many times: This check happens once per user or role creation.

How Execution Grows With Input

MongoDB uses indexes to perform a fast lookup for duplicates, regardless of the number of existing users or roles.

Input Size (n)	Approx. Operations
10	1 indexed lookup
100	1 indexed lookup
1000	1 indexed lookup

Pattern observation: The work remains constant as the number of users or roles already in the system grows.

Final Time Complexity

Time Complexity: O(log n)

This means the time to create a user or role grows logarithmically with the number of existing users or roles, which is effectively very fast and close to constant time for practical purposes.

Common Mistake

[X] Wrong: "Creating a user or role takes longer as more exist because it scans all entries."

[OK] Correct: MongoDB uses indexes on usernames and rolenames for fast O(log n) lookups, which is effectively constant time.

Interview Connect

Understanding how user and role creation scales (logarithmic time due to indexing) helps you explain system behavior clearly and shows you think about real database operations.

Self-Check

"What if we batch create 100 users at once? How would the time complexity change?"

Practice

1. What is the primary purpose of creating users in MongoDB?

easy

A. To control who can access the database

B. To store data in collections

C. To optimize query performance

D. To backup the database automatically

Solution

1. Step 1: Understand user creation in MongoDB

   Users in MongoDB are created to manage access to the database system.

2. Step 2: Identify the purpose of users

   Users control who can connect and perform actions on the database.

3. Final Answer:

   To control who can access the database -> Option A

4. Quick Check:

   Users = Access control [OK]

Hint: Users manage access, not data or backups [OK]

Common Mistakes:

• Confusing users with data storage
• Thinking users optimize queries
• Assuming users handle backups

2. Which of the following is the correct syntax to create a user with read-only access on the sales database in MongoDB?

easy

A. db.createUser({user: 'reader', pwd: 'pass', roles: [{role: 'read', db: 'sales'}]})

B. db.createUser({user: 'reader', pwd: 'pass', roles: ['read']})

C. db.addUser('reader', 'pass', 'read')

D. db.users.insert({user: 'reader', pwd: 'pass', role: 'read'})

Solution

1. Step 1: Recall MongoDB user creation syntax

   The correct syntax uses db.createUser() with roles as an array of objects specifying role and database.

2. Step 2: Check each option

   db.createUser({user: 'reader', pwd: 'pass', roles: [{role: 'read', db: 'sales'}]}) correctly specifies the role 'read' on the 'sales' database. db.createUser({user: 'reader', pwd: 'pass', roles: ['read']}) misses the database name, C uses deprecated syntax, D tries to insert directly into users collection which is invalid.

3. Final Answer:

   db.createUser({user: 'reader', pwd: 'pass', roles: [{role: 'read', db: 'sales'}]}) -> Option A

4. Quick Check:

   Roles need role and db fields [OK]

Hint: Roles need role and db fields in array [OK]

Common Mistakes:

• Omitting the database in roles
• Using deprecated addUser method
• Trying to insert user directly into collection

3. Given the following command in MongoDB shell:

db.createUser({user: 'adminUser', pwd: 'secure123', roles: [{role: 'userAdminAnyDatabase', db: 'admin'}]})

What permission does the user adminUser have?

medium

A. Can read data from any database

B. Can manage users on any database

C. Can only read the admin database

D. Can write data to any database

Solution

1. Step 1: Understand the role userAdminAnyDatabase

   This role allows managing users and roles across all databases.

2. Step 2: Analyze the permissions given

   The user can create, modify, and delete users on any database but does not have read or write data permissions by default.

3. Final Answer:

   Can manage users on any database -> Option B

4. Quick Check:

   userAdminAnyDatabase = user management [OK]

Hint: userAdminAnyDatabase manages users, not data [OK]

Common Mistakes:

• Assuming it grants read or write data access
• Confusing admin database with all databases
• Thinking it only applies to admin database

4. You try to create a user with this command:

db.createUser({user: 'testUser', pwd: 'test123', roles: ['readWrite']})

But it fails. What is the most likely reason?

medium

A. Password is too short

B. User already exists

C. Roles must be objects specifying role and database

D. Missing database name in createUser command

Solution

1. Step 1: Check roles format in createUser

   Roles must be an array of objects with role and db fields, not just strings.

2. Step 2: Identify the error cause

   The command uses roles as strings, which is invalid syntax causing failure.

3. Final Answer:

   Roles must be objects specifying role and database -> Option C

4. Quick Check:

   Roles = [{role: '', db: ''}] [OK]

Hint: Roles need role and db objects, not strings [OK]

Common Mistakes:

• Using role names as plain strings
• Ignoring role database specification
• Assuming password length causes failure

5. You want to create a custom role named reportViewer that allows users to only read data from the reports collection in the analytics database. Which command correctly creates this role?

hard

A. db.createRole({role: 'reportViewer', privileges: [{resource: {db: 'analytics', collection: 'reports'}, actions: ['read']}], roles: []})

B. db.createRole({role: 'reportViewer', privileges: [{resource: {db: 'analytics'}, actions: ['read']}], roles: []})

C. db.createRole({role: 'reportViewer', privileges: [{resource: {collection: 'reports'}, actions: ['find']}], roles: []})

D. db.createRole({role: 'reportViewer', privileges: [{resource: {db: 'analytics', collection: 'reports'}, actions: ['find']}], roles: []})

Solution

1. Step 1: Understand custom role creation syntax

   Custom roles require specifying privileges with resource (db and collection) and actions allowed.

2. Step 2: Analyze each option's privileges

   db.createRole({role: 'reportViewer', privileges: [{resource: {db: 'analytics', collection: 'reports'}, actions: ['find']}], roles: []}) correctly specifies the database 'analytics', collection 'reports', and action 'find' which allows reading documents. db.createRole({role: 'reportViewer', privileges: [{resource: {db: 'analytics'}, actions: ['read']}], roles: []}) uses 'read' action on the whole database, not just the collection. db.createRole({role: 'reportViewer', privileges: [{resource: {collection: 'reports'}, actions: ['find']}], roles: []}) misses the database name. db.createRole({role: 'reportViewer', privileges: [{resource: {db: 'analytics', collection: 'reports'}, actions: ['read']}], roles: []}) uses 'read' action which is not a valid action for privileges; 'find' is correct for reading documents.

3. Final Answer:

   db.createRole({role: 'reportViewer', privileges: [{resource: {db: 'analytics', collection: 'reports'}, actions: ['find']}], roles: []}) -> Option D

4. Quick Check:

   Custom role needs db, collection, and 'find' action [OK]

Hint: Use 'find' action for read on specific collection [OK]

Common Mistakes:

• Using 'read' action instead of 'find'
• Omitting database name in resource
• Specifying collection without database