Hash-based sharding in MongoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable sharding on the database named 'sales'.

MongoDB

sh.enableSharding('[1]')

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

Ainventory

Bsales

Cusers

Dconfig

Attempts:

3 left

💡 Hint

Common Mistakes

Using a collection name instead of a database name.

Forgetting to put the database name in quotes.

To enable sharding on a database, you use sh.enableSharding() with the database name. Here, 'sales' is the correct database.

2fill in blank

medium

Complete the code to shard the collection 'orders' in the 'sales' database using a hashed shard key on the field 'orderId'.

MongoDB

sh.shardCollection('sales.orders', { [1]: 'hashed' })

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

AcustomerId

Bstatus

Cdate

DorderId

Attempts:

3 left

💡 Hint

Common Mistakes

Using a field that is not the shard key.

Not specifying the shard key field correctly.

The shard key field is 'orderId' and it must be specified as the key with the value 'hashed' to use hash-based sharding.

3fill in blank

hard

Fix the error in the code to shard the collection 'products' in the 'inventory' database using a hashed shard key on 'productId'.

MongoDB

sh.shardCollection('inventory.products', { [1]: 'hashed' })

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

Aproduct_id

BprodId

CproductId

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using a similar but incorrect field name.

Ignoring case sensitivity in field names.

The shard key must match the exact field name used in the documents. Here, 'productId' is the correct field name.

4fill in blank

hard

Fill both blanks to create a hashed shard key on the 'customerId' field for the 'clients' collection in the 'crm' database.

MongoDB

sh.shardCollection('[1].clients', { [2]: 'hashed' })

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

Acrm

Borders

CcustomerId

Dclients

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping database and collection names.

Using the wrong field as shard key.

The database name is 'crm' and the shard key field is 'customerId'. Both must be correctly placed in the command.

5fill in blank

hard

Fill all three blanks to enable sharding on the 'analytics' database, then shard the 'events' collection using a hashed shard key on 'eventId'.

MongoDB

sh.enableSharding('[1]');
sh.shardCollection('[2].[3]', { eventId: 'hashed' })

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

Aanalytics

Cevents

Dlogs

Attempts:

3 left

💡 Hint

Common Mistakes

Using different database names in enableSharding and shardCollection.

Using the wrong collection name.

First, enable sharding on the 'analytics' database. Then shard the 'events' collection in the same database using 'eventId' as the hashed shard key.