Learn Testcontainers with Java – Module 2 Lesson 2

Quiz Summary

0 of 5 Questions completed

Questions:

You have already completed the quiz before. Hence you can not start it again.

Quiz is loading…

You must sign in or sign up to start the quiz.

You must first complete the following:

Results

Quiz complete. Results are being recorded.

Results

0 of 5 Questions answered correctly

Your time:

You have reached 0 of 0 point(s), (0)

Question 1 of 5

1. Question

What is distinct about MongoDBContainer compared to PostgreSQLContainer in terms of container configuration?

MongoDBContainer requires a separate initialization script to configure the database name
Correct Incorrect Correct answer

MongoDBContainer does not provide withUsername(), withPassword(), or withDatabaseName() methods because MongoDB starts without authentication by default in a test context
Correct Incorrect Correct answer

MongoDBContainer must be configured with a specific MongoDB version using withMongoVersion()
Correct Incorrect Correct answer

MongoDBContainer automatically creates a named database based on the test class name
Correct Incorrect Correct answer

Correct

Incorrect
Question 2 of 5

2. Question

How do we obtain the correct connection details to connect to a MongoDBContainer from a test?

We hardcode the default MongoDB port (27017) since Testcontainers always maps to that same port
Correct Incorrect Correct answer

We call getMappedPort(27017) and construct the URI manually
Correct Incorrect Correct answer

We read the connection string from the container's environment variables after startup
Correct Incorrect Correct answer

We call getConnectionString(), which returns a fully constructed mongodb:// URI that includes the correct host and dynamically mapped port
Correct Incorrect Correct answer

Correct

Incorrect
Question 3 of 5

3. Question

Why do we create the MongoClient in @BeforeAll rather than in @BeforeEach?

@BeforeEach does not support static references and cannot hold the client
Correct Incorrect Correct answer

MongoClients.create() is not thread-safe and must be called before the test runner initializes
Correct Incorrect Correct answer

The client holds a network connection to the container, so creating it once in @BeforeAll avoids the overhead of recreating it before every test method
Correct Incorrect Correct answer

@BeforeAll is required by the @Testcontainers extension whenever a container is declared as static
Correct Incorrect Correct answer

Correct

Incorrect
Question 4 of 5

4. Question

Why do we call collection.drop() in @BeforeEach before inserting test data?

drop() is required to register the collection with MongoDB before inserting new documents
Correct Incorrect Correct answer

Without it, insertMany() throws an exception if the collection already contains documents
Correct Incorrect Correct answer

To prevent one test from seeing documents inserted by a previous test, ensuring each test starts with a clean, isolated state
Correct Incorrect Correct answer

To reset the internal collection sequence counter so document IDs start from zero for each test
Correct Incorrect Correct answer

Correct

Incorrect
Question 5 of 5

5. Question

How does setting up test data in MongoDBContainer differ from PostgreSQLContainer?

MongoDBContainer uses a JSON schema file equivalent to the withInitScript() method used in SQL containers
Correct Incorrect Correct answer

Both containers support withInitScript(), but MongoDB scripts use a .js extension instead of .sql
Correct Incorrect Correct answer

MongoDBContainer automatically populates data from JSON files placed in the resources folder
Correct Incorrect Correct answer

Unlike SQL containers, MongoDBContainer does not support withInitScript(), so we insert documents programmatically using the MongoClient API
Correct Incorrect Correct answer

Correct

Incorrect

Learn Testcontainers with Java – Module 2 Lesson 2 – Quiz

Quiz Summary

Information

Results

Results

Categories

1. Question

2. Question

3. Question

4. Question

5. Question