IBM Certified Developer - Cloud Native Java with IBM Liberty Free Sample Questions

The @CircuitBreaker annotation is designed specifically for this use case. It follows the circuit breaker pattern, where after a configured number of consecutive failures (requestVolumeThreshold), the circuit 'opens' and subsequent calls fail immediately without attempting to contact the failing service. After a delay (delay), it enters a 'half-open' state to test if the service has recovered. @Retry would repeatedly call the failing service, potentially worsening the problem. @Timeout only limits the duration of a single call, it does not prevent future calls. @Fallback provides an alternative execution path on failure but does not stop calls to the original service.

The bootstrap.properties file is specifically designed for setting properties that are needed before the main server.xml configuration is processed. It has a higher precedence for system properties than server.xml. This makes it ideal for setting early-stage configuration, such as properties that control the configuration parsing itself or sensitive values that should be externalized from the main configuration file.

MicroShed Testing is a framework built on top of Testcontainers and JUnit 5, specifically for testing Jakarta EE and MicroProfile applications. It excels at starting the application in a Docker container alongside its dependencies (like databases or other services), creating a true-to-production test environment. Mockito is for mocking objects (unit tests), Pact is for contract testing, and JUnit 5 is a general testing framework that does not inherently manage containerized dependencies.

Mutual TLS (mTLS) is the correct mechanism for this scenario. In mTLS, not only does the client verify the server's certificate (standard one-way TLS), but the server also demands and verifies the client's certificate. This ensures both parties are who they claim to be, establishing a strong, mutually authenticated identity at the transport layer, which is a cornerstone of zero-trust network security. JWT is for application-level authentication/authorization, not transport-level identity verification. OpenID Connect is for user authentication.

This is a correct implementation. The class is annotated with @Readiness to mark it as a readiness probe, it implements the HealthCheck interface, and the call() method returns a HealthCheckResponse indicating the status.

This is also a correct implementation. It uses the HealthCheckResponse builder pattern to construct the response, dynamically setting the status based on the result of the checkDatabase() method. The @Readiness annotation correctly designates it for readiness checks.

False. The 'zero migration' principle applies to the Liberty runtime itself, meaning you can update the runtime without changing your application or its configuration. However, it does not apply to major specification changes like the move from Jakarta EE 8 to Jakarta EE 10. This move involves a package name change from javax.* to jakarta.*, which requires significant code changes. The application would need to be recompiled against the new Jakarta EE 10 APIs.

Liberty dev mode relies on detecting changes to compiled .class files. If the Integrated Development Environment (IDE) is not automatically compiling the Java source files upon saving, dev mode will not detect any changes and will not trigger a hot reload.

If the code change introduced a compilation error, the .class file will not be updated. Since dev mode monitors the compiled output directory, it will not see a new file and therefore will not reload the application. The developer would need to check their IDE's problem view or run a manual build to see the error.

Factor III, 'Config', states that configuration should be stored in the environment and strictly separated from the code. Hardcoding connection details in server.xml violates this principle because the configuration is bundled with the deployable artifact. The correct approach is to externalize this configuration using environment variables or a configuration service, which can then be injected into the application at runtime via MicroProfile Config.

Jakarta Bean Validation is the standard specification for this purpose. By annotating the fields of the payload model class (POJO) with constraints like @Size(min=12) and @Pattern(regexp=...), the validation logic is kept declarative and separate from the business logic. When the JAX-RS method is annotated with @Valid, the Liberty runtime will automatically trigger the validation and return a 400 Bad Request if the constraints are violated.

The correct and simplest method to enable structured JSON logging in Open Liberty is to add the attribute messageSource="json" to the element in server.xml. This instructs Liberty to write log records for messages.log and trace.log in JSON format, which includes fields like timestamp, log level, message, thread ID, and other context, making them easily parsable by log aggregation tools.