How to prevent a MongoDB user from creating a collection with the same name as an existing collection?

Question

THIS BLOCK IS THE SAME FOR ALL QUESTIONS

> You must design a landscaper marketplace.

> A person can register as a landscaper. She then chooses the services she offers from a pre-established list. She then declares - by selecting on a calendar - her availability (a start date and an end date, the days are always whole).

> Another person can register on the site as a client. She can then select the one or more services she is looking for. A list of landscapers is then presented to her with a filter that allows only landscapers available for certain days / periods to be presented.

> If the client finds an adequate landscaper, he can then select the dates he actually needs and then place an order.

> All the questions of the quiz refer to this problem.
> -----  
> ####Two important constraints are added to answer the questions:

>  No data redundancy is tolerated.

>  We will consider the storage of structured data (array, hash, json, etc.) in a single data field impossible.

You decide to model as follows:

```java
# collection landscapers
{
  _id: ObjectId("4c0791e2b9ec877893f3363a"),
  name: "John Lennon",
  services:["sculpture", "labyrinth"]
}
```

The list of possible services is stopped in advance. How do you ensure that the written values are part of this list?

Accepted Answer

By adding checks in the database client application

Answer

By adding constraints on the landscapers collection

Answer

The insertion transactions are sufficient to validate the data

Answer

It is impossible

Question from the MongoDB test

How to prevent a MongoDB user from creating a collection with the same name as an existing collection?

All the questions of the quiz refer to this problem.