Lab 1.1

Welcome to your first lab in M201! In this lab you're going to install MongoDB Enterprise 3.4 and import the people dataset.

 While MongoDB Enterprise is available as part of the MongoDB Enterprise Advanced subscription it's permitted to be ran outside of production environments.

 In order to install MongoDB you're going to need to head over to our online documentation and follow the instructions on installing MongoDB.

 After you've successfully installed MongoDB you should start a standalone server. Once your sever is up and running you should be able to download the people.json handout and import it with mongoimport. Make sure to import the documents into the m201 database and the people collection.

 To confirm that you've successfully completed these steps run the following query on the m201 database from the mongo shell and paste it's output into the submission area below:

 > db.people.count({ "email" : {"$exists": 1} })
Answer: 50474

 Installed MongoDB & start it & imported people collection into m201 db.




Executed the above command:







Comments

  1. idanasadeghi4 March 2022 at 06:56

    Casino Near Me - Mapyro
    Looking for 충청남도 출장마사지 a 대전광역 출장안마 Casino Near Me? MapYRO is your top pick for valuable information 강원도 출장안마 about 속초 출장안마 Casinos Near Me. Use our detailed MapYRO to quickly and easily 천안 출장안마 find

    ReplyDelete

Post a Comment

Popular posts from this blog

M201 MongoDB Performance - Labs & Final Exam Q&A

M201 MongoDB Performance Chapter-1 Introduction to MongoDB Performance Lab 1.1: Install Course Dependencies Lab 1.2: Install MongoDB Compass Chapter – 2 MongoDB Indexes Lab 2.1: Using Indexes to Sort Lab 2.2: Optimizing Compound Indexes Chapter – 3 Index Operations Lab 3.1: Explain Output Chapter 4: CURD Optimization Lab 4.1 – Equality, Sort, Range Chapter 5: Performance on Clusters Final Exam Question 1 Question 2 Question 3 Question 4 Question 5 Question 6 Question 7
Read more

Question 1

Image
Which of these statements is/are true? Answer: You can index multiple array fields in a single document with a single compound index - False   Multikey indexes allow us to index on array fields, but they do not support indexes on multiple array fields on single documents. Covered queries can sometimes still require some of your documents to be examined - False A query is covered if and only if it can be satisfied using the keys of the index. Write concern has no impact on write latency - False Different write concerns can certainly impact your write latency. Write concerns that only need acknowledgment from a primary are generally faster than ones that need acknowledgment from a majority of replica set members. Creating an ascending index on a monotonically increasing value creates index keys on the right-hand side of the index tree - True A collection scan has a logarithmic search time - False No, collection scans have a  linear  search time.
Read more

Question 7

Image
Given the following indexes: { categories: 1, price: 1 } { in_stock: 1, price: 1, name: 1 } The following documents: { price: 2.99, name: "Soap", in_stock: true, categories: ['Beauty', 'Personal Care'] } { price: 7.99, name: "Knife", in_stock: false, categories: ['Outdoors'] } And the following queries: db.products.find({ in_stock: true, price: { $gt: 1, $lt: 5 }  }).sort({  name: 1 }) db.products.find({ in_stock: true }) db.products.find({ categories: 'Beauty'  }).sort({  price: 1 }) Whic h of  following is/are true? Answer: Index #1 would provide a sort to query #3. - True Index #2 properly uses the equality, sort, range rule for query #1. - False - If we were to build an index for query #1 using the equality, sort, range rule, then the index would be: { in_stock: 1, name: 1, price: 1 }. There would be a total of 4 index keys created across all of these documents and indexes. - False - As there would be 5 to
Read more