The Red Hat Certified Enterprise Microservices Developer exam (EX283) tests your skills and knowledge to develop reliable, performant JEE applications in a microservices-style environment. The exam focuses on using the Microprofile APIs to develop microservices enterprise Java applications.
If you are a current Red Hat Certified Enterprise Application Developer (RHCEAD), you will become a Red Hat Certified Enterprise Microservices Developer by passing this exam.
If you are a current Red Hat Certified JBoss Developer (RHCJD), you will become a Red Hat Certified Specialist in Enterprise Microservices Development by passing this exam. Anyone can take this exam, but you must be either an RHCEAD or an RHCJD in order to become a Red Hat Certified Enterprise Microservices Developer.
This exam is based on Eclipse MicroProfile 1.3.
Note on the exam:
Cancelations of the purchase: Cancelation of individual exam sessions is not allowed. Exam session fees are nonrefundable. Non-Cancelable components: No part of any Bundles that includes both non-cancelable and cancelable components may be canceled.
Moyens Pédagogiques :
- Réalisation de la formation par un formateur agréé par l’éditeur
- Formation réalisable en présentiel ou en distanciel
- Mise à disposition de labs distants/plateforme de lab pour chacun des participants (si applicable à la formation)
- Distribution de supports de cours officiels en langue anglaise pour chacun des participants
- Il est nécessaire d'avoir une connaissance de l'anglais technique écrit pour la compréhension des supports de cours
- Accessibilité aux Personnes en Situation de Handicap – nous contacter
Moyens d'évaluation :
- Évaluations formatives pendant la formation, à travers les travaux pratiques réalisés sur les labs à l’issue de chaque module
- Évaluation sous forme de questionnaire à l’issue de la formation
Who should attend
JEE developers who wish to demonstrate their skills and abilities using Java to develop advanced, microservices-oriented enterprise applications.
- Pass or have equivalent industry JEE experience
- Be familiar with using Red Hat® JBoss® Developer Studio in a Red Hat® Enterprise Linux environment
- Have a solid background with JEE, including a knowledge and understanding of the core Java concepts and APIs. For example, exceptions, annotations, and the collections API are all required during the exam
- Some familiarity with Openshift is beneficial
Red Hat encourages you to consider takingto help prepare. Attendance in these classes is not required; students can choose to take just the exam.
While attending Red Hat classes can be an important part of one's preparation to take this exam, attending class does not guarantee success on the exam. Previous experience, practice, and native aptitude are also important determinants of success.
Many books and other resources on system administration for Red Hat's products are available. Red Hat does not officially endorse any as preparation guides for its exam. Nevertheless, you may find additional reading deepens understanding and can prove helpful.
This exam is a hands-on, practical exam that requires you to undertake real-world development tasks. Internet access is not provided during the exam, and you will not be permitted to bring any hard copy or electronic documentation into the exam. This prohibition includes notes, books, or any other material. MicroProfile specification and related documentation is available during the exam.
Official scores for exams come exclusively from Red Hat Certification Central. Red Hat does not authorize examiners or training partners to report results to candidates directly. Scores on the exam are usually reported within 3 US business days.
Exam results are reported as total scores. Red Hat does not report performance on individual items, nor will it provide additional information upon request.
You should be able to accomplish the tasks below without assistance. While explicitly addressing Microprofile and microservices, the skills and abilities demonstrated in this exam are also applicable to a wide range of advanced enterprise Java developments:
Provide and obtain configuration properties through several environment-aware sources both internal and external to the application and made available through dependency injection or lookup using Configuration for Microprofile
- Externalize data into configured values
- Inject configured values into beans using the @Inject and the @ConfigProperty qualifier
- Access or create a certain configuration
- Understand default and custom ConfigSource and ConfigSource ordering
- Understand and implement converters
Separate execution logic from business logic using Microprofile Fault Tolerance
- Understand the relationship to MicroProfile Config
- Understand async vs. sync execution type and know the default
- Use @Timeout
- Understand retry policies and apply using @Retry
- Understand and define fallback
- Understand and apply CircuitBreaker and Bulkhead
- Understand and set up fault tolerance configuration
Probe the state of a computing node from another machine using MicroProfile Health Check
- Understand and implement the Health Check interface and Health Check Response
- Construct human-friendly Health Check Response
- Understand protocol and wireformat
Export monitoring data to management agents using Microprofile Metrics
- Understand difference with Health Check
- Understand and use three sets of sub-resource (scopes): base, vendor, and application
- Understand tags (labels), metric registry, and @Metric
- Understand metadata and why it is best practice
- Expose metrics via REST API
- Know required metrics
- Understand application metrics programming model
MicroProfile Interoperable JWT RBAC: OpenID Connect (OIDC)–based JSON Web Tokens (JWTs) for role-based access control (RBAC) of microservice endpoints
- Understand security tokens in RESTful services and token-based authentication
- Use JWT bearer tokens to protect services
- Mark a JAX-RS application as requiring MP-JWT access control
- Map MP-JWT tokens to Java EE Container APIs
As with all Red Hat performance-based exams, configurations must persist after reboot without intervention.