I B M C E R T I F I C A T I O N
C9004800 IBM Certified Developer – Cloud Native Java with IBM Liberty 2023 Practice Exam
Exam Number: 4387 | Last updated April 17, 2026 | 395+ questions across 5 vendor-aligned objectives
Liberty Java developers who build cloud-native applications using IBM Liberty 2023 target the C9004800 credential. The exam validates your ability to design twelve-factor applications using Jakarta EE and MicroProfile on Liberty, run them as containers, and integrate with cloud services. Candidates should be fluent with server.xml configuration, MicroProfile features, Jakarta EE 10 specifications, and the container-friendly aspects of Liberty’s runtime.
Enveloping 26% of the exam, Liberty and Jakarta EE Fundamentals covers server.xml, feature composition, Jakarta EE 10 specifications, and server configuration. At 22%, MicroProfile covers Config, Health, Metrics, OpenAPI, Rest Client, Fault Tolerance, and JWT. A further 20% targets Container and Cloud-Native Patterns, covering Dockerfiles, InstantOn, and Liberty in Kubernetes and OpenShift contexts.
Sanding down the remaining domains, Data Access and Persistence accounts for 18% and spans JPA, data-source configuration, and cloud-database connectivity. Security and Identity represents 14% and spans JWT, OAuth, and LDAP in Liberty. Developer questions often test specific MicroProfile APIs with enough precision to distinguish Fault Tolerance annotations from each other — memorize them.
Every answer links to the source. Each explanation below includes a hyperlink to the exact IBM documentation page the question was derived from. PowerKram is the only practice platform with source-verified explanations. Learn about our methodology →
751
practice exam users
94%
satisfied users
91%
passed the exam
4.7/5
quality rating
Test your C9004800 liberty java 2023 knowledge
10 of 395+ questions
Question #1 - Liberty and Jakarta EE Fundamentals
A Liberty 2023 developer at Brathmere Bank needs to enable only the Jakarta EE specifications the application uses.
Which Liberty 2023 feature-manager configuration fits the targeted Jakarta EE features?
A) In server.xml
B) Enable every feature available in Liberty 2023
C) Skip the featureManager section entirely
D) Put feature declarations in the application jar rather than server.xml
Show solution
Correct answers: A – Explanation:
Feature-manager declarations matching actual use is the Liberty 2023 reference. Enabling-everything, no-featureManager, and in-jar declarations all fail feature composition. Source: Check Source
Question #2 - Liberty and Jakarta EE Fundamentals
A Liberty 2023 developer at Plumley Retail deploys a Jakarta RESTful Web Services endpoint.
Which Liberty 2023 configuration deploys the Jakarta REST endpoint?
A) Enable the restfulWS feature in server.xml and implement the resource class with Jakarta EE 10 @Path and @GET/@POST annotations, letting Liberty route requests to the resource
B) Skip the restfulWS feature and hope endpoints appear
C) Use a custom HTTP server outside Liberty for REST
D) Write servlets by hand that bypass Jakarta REST
Show solution
Correct answers: A – Explanation:
restfulWS feature @Path resources is the Liberty 2023 Jakarta REST reference. No-feature, external HTTP servers, and hand-written servlets all miss Jakarta REST. Source: Check Source
Question #3 - MicroProfile
A Liberty 2023 developer at Norsford Credit needs a readiness endpoint that reflects service dependencies.
Which MicroProfile specification fits?
A) Skip readiness endpoints entirely
B) Return a static 200 regardless of dependencies
C) MicroProfile Health with @Readiness-annotated checks, exposing /health/ready so Kubernetes readiness probes route traffic only when dependencies are healthy
D) Use a custom endpoint with no standard path
Show solution
Correct answers: C – Explanation:
MicroProfile Health @Readiness is the Liberty 2023 reference. Static 200s, no-endpoint, and non-standard paths all fail readiness design. Source: Check Source
Question #4 - MicroProfile
A Liberty 2023 developer at Trebleford Logistics must call a remote service via a type-safe REST client.
Which MicroProfile API provides a type-safe REST client for the remote call?
A) MicroProfile Rest Client with a type-safe interface annotated with Jakarta REST annotations, generating the client at runtime and letting the developer call methods instead of hand-building HTTP requests
B) Build HTTP calls by hand with URLConnection
C) Skip remote calls and mock everything
D) Use an unrelated non-MicroProfile client with no fault tolerance
Show solution
Correct answers: A – Explanation:
MicroProfile Rest Client is the Liberty 2023 type-safe REST reference. URLConnection hand-builds, mock-only, and non-MP clients all miss the feature. Source: Check Source
Question #5 - MicroProfile
A Liberty 2023 developer at Harnwicks Insurance needs to apply a circuit-breaker and timeout to a remote call.
Which MicroProfile API applies circuit-breaker and timeout behavior to the remote call?
A) Implement the circuit breaker by hand in a thread
B) MicroProfile Fault Tolerance annotations — @Timeout and @CircuitBreaker — on the method calling the remote service, with a @Fallback for graceful degradation
C) Skip timeouts and fault-tolerance entirely
D) Catch every exception silently without fallback
Show solution
Correct answers: B – Explanation:
MicroProfile Fault Tolerance @Timeout @CircuitBreaker @Fallback is the Liberty 2023 resilience reference. Hand-threaded breakers, no-fault-tolerance, and silent catches all fail the pattern. Source: Check Source
Question #6 - Container and Cloud-Native Patterns
A Liberty 2023 developer at Frydstone Bank wants fast startup for a serverless-like workload.
Which Liberty 2023 capability fits?
A) Disable all features to make startup faster
B) Accept multi-second startup for every launch
C) Skip Liberty and rewrite the app in a different language for cold-start
D) Use Liberty InstantOn to capture an application snapshot after startup so subsequent launches resume from the snapshot, reducing effective startup time for scale-to-zero or fast-cold-start scenarios
Show solution
Correct answers: D – Explanation:
Liberty InstantOn for fast cold start is the Liberty 2023 container reference. Default startup, language rewrites, and feature disabling all miss the capability. Source: Check Source
Question #7 - Container and Cloud-Native Patterns
A Liberty 2023 developer at Mulderwood Retail builds a container image for an application.
Which Liberty 2023 Dockerfile approach fits?
A) Skip the container image and run Liberty on bare metal only
B) Start from a random Alpine image and manually install Liberty
C) Embed the server.xml inside the application source and skip the Liberty base image
D) Use the official Liberty base image, copy the application WAR and required server.xml into the image per the Liberty container documentation, and expose the configured port
Show solution
Correct answers: D – Explanation:
Official Liberty base image copy-WAR copy-server.xml expose port is the Liberty 2023 container reference. Random base images, no-base-image, and no-container all fail container practice. Source: Check Source
Question #8 - Data Access and Persistence
A Liberty 2023 developer at Spearsworth Finance uses JPA to persist entities.
Which Liberty 2023 configuration enables JPA persistence with a configured data source?
A) Skip the jpa feature and hope JPA just works
B) Enable the jpa feature in server.xml, configure a
C) Configure a dataSource without a JDBC driver
D) Hard-code database credentials in the entity class
Show solution
Correct answers: B – Explanation:
jpa feature dataSource persistence.xml JNDI is the Liberty 2023 data-access reference. No-feature, driver-less, and hard-coded creds all fail persistence. Source: Check Source
Question #9 - Data Access and Persistence
A Liberty 2023 developer at Wyndcoln Retail connects to a cloud database like Db2 on Cloud.
Which Liberty 2023 approach connects to the Db2 on Cloud managed database?
A) Skip data-source configuration and use a random HTTP endpoint
B) Hard-code the cloud database password in server.xml
C) Configure a Liberty
D) Copy the database locally into the container and query stale data
Show solution
Correct answers: C – Explanation:
Liberty dataSource externalized credentials JNDI is the 2023 cloud-database reference. Hard-coded creds, HTTP hacks, and local copies all fail cloud data-access. Source: Check Source
Question #10 - Security and Identity
A Liberty 2023 developer at Nevinwick Bank must accept JWT tokens issued by a corporate identity provider.
Which Liberty 2023 approach accepts JWT tokens from the corporate IdP?
A) Roll a custom JWT parser and skip signature validation
B) Enable the mpJwt feature with the corporate IdP’s JWKS URL configured, and annotate Jakarta REST resources with @RolesAllowed so tokens are validated and authorization enforced by Liberty
C) Skip authentication entirely
D) Trust every JWT regardless of issuer or signature
Show solution
Correct answers: B – Explanation:
mpJwt with JWKS @RolesAllowed is the Liberty 2023 JWT reference. Custom unvalidated parsers, no-auth, and trust-everything all fail JWT security. Source: Check Source
Get 395+ more questions with source-linked explanations
Every answer traces to the exact IBM documentation page — so you learn from the source, not just memorize answers.
Exam mode & learn mode · Score by objective · Updated April 17, 2026
Learn more...
What the C9004800 liberty java 2023 exam measures
- Configure and compose server.xml, Liberty features, Jakarta EE 10, and server configuration to build Liberty servers that match application needs without unused features
- Apply and combine MicroProfile Config, Health, Metrics, OpenAPI, Rest Client, Fault Tolerance, and JWT to leverage cloud-native patterns that make applications observable and resilient
- Containerize and deploy Dockerfiles, InstantOn, and Liberty on Kubernetes and OpenShift to ship Liberty workloads as cloud-native containers with fast startup
- Persist and connect JPA, data-source configuration, and cloud-database connectivity to connect Liberty applications to both legacy and cloud-native data stores
- Secure and authenticate JWT, OAuth, and LDAP in Liberty to enforce identity and access control consistently across Liberty applications
How to prepare for this exam
- Review the official exam guide to understand every objective and domain weight before you begin studying
- Work through the relevant IBM Training learning path — ibm certified developer cloud native java with ibm liberty 2023 C9004800 — to cover vendor-authored material end-to-end
- Get hands-on inside IBM TechZone or a comparable sandbox so you can practice the console tasks, CLI commands, and APIs the exam expects
- Tackle a real-world project at your workplace, a volunteer role, or an open-source repository where the technology under test is actually in use
- Drill one exam objective at a time, starting with the highest-weighted domain and only moving on once you can teach it to someone else
- Study by objective in PowerKram learn mode, where every explanation links back to authoritative IBM documentation
- Switch to PowerKram exam mode to rehearse under timed conditions and confirm you consistently score above the pass mark
Career paths and salary outlook
Modern Liberty Java developers are prized as enterprises modernize toward cloud-native Jakarta EE applications:
- Cloud-Native Java Developer — $110,000–$150,000 per year, building Jakarta EE and MicroProfile apps on Liberty (Glassdoor salary data)
- Senior Java Developer — $125,000–$165,000 per year, leading Java modernization for enterprise workloads (Indeed salary data)
- Application Platform Developer — $120,000–$160,000 per year, owning Liberty-based application platforms (Glassdoor salary data)
Official resources
Work through the official IBM Training learning path for this certification, which bundles videos, labs, and skill tasks aligned to every objective. The official exam page lists the full objective breakdown, prerequisite knowledge, and scheduling details.