MongoDB Associate DBA - Study Strategy¶
Study Approach¶
Phase 1: Server Fundamentals (1-2 weeks)¶
- mongod Configuration
- Master mongod configuration file format
- Understand WiredTiger storage engine internals
- Learn journaling and durability mechanisms
-
Study server commands and diagnostics
-
Hands-on Setup
- Install MongoDB locally and configure mongod.conf
- Deploy standalone instance with custom configuration
- Practice server management commands
- Explore log files and server status output
Phase 2: Replication and Sharding (2-3 weeks)¶
- Replication
- Deploy a 3-node replica set
- Practice elections and failover scenarios
- Configure read preferences and write concerns
-
Study oplog mechanics and sizing
-
Sharding
- Deploy a sharded cluster (config servers, mongos, shards)
- Practice shard key selection for different workloads
- Study chunk management and the balancer
- Configure zone-based sharding
Phase 3: Security, Backup, and Monitoring (2-3 weeks)¶
- Security
- Configure SCRAM authentication
- Set up TLS/SSL encryption
- Implement role-based access control
-
Practice user and role management
-
Backup and Monitoring
- Practice mongodump and mongorestore
- Set up database profiler
- Monitor with mongostat and mongotop
- Analyze server metrics and performance
Phase 4: Exam Preparation (1 week)¶
- Practice Exams
- Take practice exams and review answers
-
Focus on Server Admin (25%) and Replication/Sharding (40% combined)
-
Final Review
- Review configuration defaults
- Review replica set member types and roles
- Review shard key selection criteria
Study Resources¶
Official Resources¶
- π MongoDB University - DBA Path - Free DBA courses
- π MongoDB Administration - Admin reference
- π Production Notes - Production guide
- π MongoDB Manual - Complete reference
Practice¶
- π MongoDB Atlas - Free tier for practice
- π MongoDB Enterprise - Enterprise features
- π MongoDB Tools - CLI tools reference
Exam Tactics¶
Domain Priorities (by weight)¶
- Server Administration (25%) - Configuration and storage engine
- Replication (20%) - Replica sets and failover
- Sharding (20%) - Shard keys and cluster management
- Security (15%) - Auth, roles, encryption
- Backup/Recovery (10%) - Backup methods and restore
- Monitoring (10%) - Metrics and profiling tools
Key Areas to Master¶
- mongod.conf structure and key settings
- WiredTiger cache sizing and behavior
- Replica set election rules and priority
- Shard key selection criteria and trade-offs
- Authentication methods and built-in roles
- mongodump/mongorestore options
Common Pitfalls¶
- WiredTiger cache is not total memory - It uses 50% of RAM minus 1 GB by default
- Arbiter cannot hold data - Only votes in elections
- Shard key cannot be changed after collection is sharded (can refine with reshardCollection)
- Oplog is capped collection - Fixed size, old entries removed automatically
- Read preference secondary - May return stale data
- w: "majority" not w: "all" - Majority is most common for strong consistency
- mongodump is not a snapshot - Use with --oplog for consistency
- Hidden members can vote - They just cannot be discovered by drivers