When a chunk grows beyond the chunk size, MongoDB attempts to split th – McqOptions

MCQOPTIONS

1.	When a chunk grows beyond the chunk size, MongoDB attempts to split the chunk into smaller chunks, always based on ranges in the _____________
A.	replica set
B.	shard key
C.	tag sets
D.	all of the mentioned
Answer» D. all of the mentioned

Discussion

No Comment Found

Related MCQs

Which of the following parameter represents minimum value of the shard key range to include in the tag?
Changing the _______ option will change the port that mongod listens for incoming connections on.
sh.splitFind () Splits the chunk that contains the shard key value specified by the query at the chunk’s ______ point.
For most deployments, the default value of chunk is _____ megabytes is ideal.
With hash based partitioning, two documents with _____ shard key values are unlikely to be part of the same chunk.
With __________ enabled, the source shard archives the documents in the migrated chunks in a directory named after the collection namespace.
You can set the _________ option on the balancer configuration to set different write concern semantics.
_______ forces an update to the cluster metadata cached by a mongos.
_______ enables the balancer and waits for balancing to start.
The ______ instances are the routers for the cluster.