MongoDB Certified DBA Associate C100DBA Full Course Free

MongoDB ' s flexible document schema is a defining distinction from the conventional fixed-table model associated with relational database systems. Documents in the same MongoDB collection can contain different fields, nested structures, arrays, or representations when the application domain requires that flexibility. MongoDB can still enforce schema rules through validation, so a flexible schema does not mean the absence of governance; it means the physical model is not inherently restricted to one rigid row structure for every record. The other choices are not sufficiently distinguishing. Relational database platforms can provide replication, authentication, and horizontal partitioning or sharding techniques, so those capabilities are not unique architectural differences. MongoDB ' s BSON document model also allows data that is commonly normalized across multiple relational tables to be embedded within one application-oriented document where that design is appropriate. This can reduce joins and map more naturally to object structures used by applications. DBAs must still choose schemas carefully based on access patterns, document growth, duplication, and consistency requirements. Among the choices, Flexible Schema most accurately represents a fundamental MongoDB-versus-RDBMS difference, so option D is correct.

Study Guide reference/topic:MongoDB Architecture and Core Operations - document databases, BSON data modeling, flexible schemas, and relational-model differences.

===========

MongoDB provides db.grantRolesToUser() specifically for assigning one or more additional roles to an existing user. The method takes the username as its first argument and an array of roles as its second argument, so db.grantRolesToUser( " user1 " , [ " customRole1 " ]) is the correct choice. A role can be supplied as a simple string when it belongs to the current database or as an explicit document such as { role: " customRole1 " , db: " admin " } when the database context must be specified. Option B uses db.createUser(), which is used to create a new user rather than modify the role membership of an account that already exists. Options A and C use method names that are not the documented mongosh interfaces for this operation. Administrators should also distinguish grantRolesToUser() from grantRolesToRole(): the latter makes a user-defined role inherit other roles, whereas the former directly changes a user ' s assigned roles. Least-privilege practice requires granting only roles necessary for the user ' s responsibilities. For the requested update to the existing user, option D is correct.

Study Guide reference/topic:Security, Networking, and Encryption - user administration, role assignment, RBAC, and grantRolesToUser().

===========