Learn Testcontainers with Java – Module 3 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

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

Question 1 of 5

1. Question

What is the main cost of hardcoding localhost connection properties in application.properties?

It forces every developer who clones the project to manually install and start each backing service before the application will boot
Correct Incorrect Correct answer

Spring Boot refuses to start if any property points at localhost
Correct Incorrect Correct answer

It causes automatic fallback to an in-memory database, hiding real integration failures
Correct Incorrect Correct answer

It prevents environment-specific property overrides from taking effect at runtime
Correct Incorrect Correct answer

Correct

Incorrect
Question 2 of 5

2. Question

Why do we annotate TestcontainersConfiguration with @TestConfiguration(proxyBeanMethods = false) rather than plain @TestConfiguration?

proxyBeanMethods = false prevents the class from being registered in the application context during a production run
Correct Incorrect Correct answer

It is required whenever @Bean methods return GenericContainer instances
Correct Incorrect Correct answer

It disables container health checks so the application boots faster in development
Correct Incorrect Correct answer

Our @Bean methods never call each other, so Spring does not need to proxy the class to enforce singleton semantics on inter-method calls
Correct Incorrect Correct answer

Correct

Incorrect
Question 3 of 5

3. Question

What is the role of .with(TestcontainersConfiguration.class) in the TestLtcApp launcher?

It replaces the production @SpringBootApplication class with the test configuration
Correct Incorrect Correct answer

It registers TestcontainersConfiguration as an extra configuration source on top of the production bootstrap, making its container beans available to the running application's context
Correct Incorrect Correct answer

It scans TestcontainersConfiguration for additional application.properties overrides
Correct Incorrect Correct answer

It generates @DynamicPropertySource entries automatically from the declared containers
Correct Incorrect Correct answer

Correct

Incorrect
Question 4 of 5

4. Question

What do the startup log lines reporting a random port and the database name “test” confirm?

The container failed to apply withInitScript() and defaulted to its own database name
Correct Incorrect Correct answer

The connection timed out and Testcontainers fell back to an in-memory substitute
Correct Incorrect Correct answer

The application is wired to the throwaway container, because the port differs from the application.properties value and "test" is not the configured database name
Correct Incorrect Correct answer

The Testcontainers network proxy remapped the application's configured URL to a loopback address
Correct Incorrect Correct answer

Correct

Incorrect
Question 5 of 5

5. Question

Why is the development-time configuration placed in src/test rather than src/main?

Testcontainers is on the test classpath, and keeping the configuration in test scope avoids leaking test dependencies into the production artifact
Correct Incorrect Correct answer

@TestConfiguration can only be processed when it resides in test source directories
Correct Incorrect Correct answer

The spring-boot:test-run Maven goal refuses to load configurations from src/main
Correct Incorrect Correct answer

@ServiceConnection annotations are only supported in test-scoped source sets
Correct Incorrect Correct answer

Correct

Incorrect

Learn Testcontainers with Java – Module 3 Lesson 2 – Quiz

Quiz Summary

Information

Results

Results

Categories

1. Question

2. Question

3. Question

4. Question

5. Question