Red Hat Certified Cloud-native Developer exam (EX378) – Contenuti

Contenuti dettagliati del Corso

To help you prepare, these exam objectives highlight the task areas you can expect to see covered in the exam. Red Hat reserves the right to add, modify, and remove exam objectives. Such changes will be made public in advance.

You should be able to perform these tasks:

Provide and obtain configuration properties through several environment-aware sources made available through dependency injection or lookup

  • Externalize data into configured values.
  • Inject configured values into beans using the @Inject and the @ConfigProperty qualifier.
  • Access or create a configuration.
  • Understand default and custom ConfigSource and ConfigSource ordering.

Build fault-tolerant Quarkus-based microservices using Microprofile Fault Tolerance strategies

  • Understand the relationship to MicroProfile Config.
  • Understand async versus sync execution type.
  • Use @Timeout.
  • Understand Retry policies and apply using @Retry.
  • Understand and define Fallback.
  • Understand and apply CircuitBreaker.
  • Understand and apply Bulkhead.
  • Understand and set up fault tolerance configuration.

Probe the state of a Quarkus application from another machine using MicroProfile Health Check

  • Understand and implement the HealthCheck interface.
  • Understand and apply @Liveness and @Readiness annotation.
  • Understand and implement HealthCheckResponse.
  • Construct human-friendly HealthCheckResponse.

Export monitoring data to management agents from a running Quarkus application using Microprofile Metrics

  • Understand and use three sets of sub-resource (scopes): Base, vendor, application.
  • Understand tags (labels).
  • Understand and use metadata.
  • Understand metric registry and @Metric.
  • Expose metrics via REST API.
  • Know required metrics.
  • Understand Quarkus application metrics programming model.

MicroProfile Interoperable JWT RBAC on Quarkus applications: OpenID Connect (OIDC)-based JSON Web Tokens(JWT) for role-based access control (RBAC) of microservice endpoints

  • Understand 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.

Implement a Quarkus application and expose REST service endpoints with JAX-RS

  • Understand REST concepts, particularly the application and use of the HTTP PUT, DELETE, GET, and POST methods.
  • Know and use standard HTTP return codes.
  • Implement RESTful root resource class.
  • Expose a REST service using JAX-RS.
  • Understand and use @Path, @Produce, and @Consume.
  • Using CDI to integrate components.
  • Using bean validation to ensure data format and consistency.

Simplified JPA mapping with Panache

  • Understand the difference between the Active Record Pattern and the Repository Pattern.
  • Use basic JPA to create, read, update, and delete persistent objects and their relationships.
  • Map a bi-directional one-to-many relationship between two entities, including both sides of the association.
  • Demonstrate the ability to perform the most common Panache operations and add custom entity methods.

Microprofile OpenAPI specification to document RESTful APIs

  • Understand OpenAPI documents and the Swagger UI to discover remote services APIs.
  • Demonstrate the ability to link to semantic versioning (semver) remote service endpoints.
  • Understand how to produce the default and custom OpenAPI document to JAX-RS endpoints.

Interacting with REST APIs in Quarkus using the MicroProfile REST Client

  • Understand the type-safe approach to invoke RESTful services over HTTP using the JAX-RS APIs.
  • Understand REST concepts, particularly the application and use of the HTTP PUT, DELETE, GET, and POST methods.
  • Demonstrate the ability to create and use a REST client to connect with a remote service.
  • Parameterize and configure the REST client URI to invoke a specific remote microservice.
  • Understand and use special additional client headers.

As with all Red Hat performance-based exams, configurations must persist after restart without intervention.