EX378 Red Hat Certified Cloud-native Developer exam Free Dumps

dumps2025-05-29T11:45:55+08:00

To become a Red Hat Certified Cloud-native Developer, you need to take and pass EX378 exam. EX378 exam is a hands-on, practical exam that requires you to undertake real-world 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. We provide the latest Red Hat Certified Cloud-native Developer EX378 exam dumps, which can guarantee you pass easily. Free Red Hat Certified Cloud-native Developer EX378 exam dumps are available below.

Page 1 of 10

1. Create a configuration property for the application name and inject it into a CDI bean.

See the Explanation.

2. Externalize a boolean flag and use it to enable/disable a service method.

See the Explanation.

3. Use default values when a configuration property is missing.

See the Explanation.

4. Inject a configuration property into a constructor using MicroProfile Config.

See the Explanation.

5. Inject a property into a JAX-RS resource class.

See the Explanation.

6. Use a configuration property to control bean behavior via conditional logic.

See the Explanation.

7. Inject a list of values from a comma-separated property.

See the Explanation.

8. Inject a map of configuration values using a prefix.

See the Explanation.

9. Inject configuration property into a Quarkus scheduler job.

See the Explanation.

10. Create a reusable config value class and inject it into multiple beans.

See the Explanation.

Page 2 of 10

11. Inject AppConfig where needed.

1 1. Inject a property value into a static method using a wrapper class.

See the Explanation.

12. Inject optional configuration property and provide runtime fallback.

See the Explanation.

13. Create a REST endpoint that exposes configuration values.

See the Explanation.

14. Demonstrate programmatic access using ConfigProvider API.

See the Explanation.

15. Validate configuration value range and fail-fast on invalid input.

See the Explanation.

16. Log all injected config values from a single source.

See the Explanation.

17. Inject a long and a double type config property into a service.

See the Explanation.

18. Inject enum config property using MicroProfile Config.

See the Explanation.

19. Use a nested bean to group related configuration properties.

See the Explanation.

20. Use a configuration mapping class to centralize grouped configs.

See the Explanation.

Page 3 of 10

21. Inject a config mapping class into a REST endpoint.

See the Explanation.

22. Create a nested configuration class.

See the Explanation.

23. Create a config mapping interface using MicroProfile Config 2.0+.

See the Explanation.

24. Access and print all configuration properties from all ConfigSources.

See the Explanation.

25. List all ConfigSources and their priorities.

See the Explanation.

26. Create a custom ConfigSource that loads properties from a custom file.

See the Explanation.

27. Override a config property with an environment variable.

See the Explanation.

28. Demonstrate the default ordering of config sources.

See the Explanation.

29. META-INF/microprofile-config.properties C ordinal 100

You can test which value is picked when you set a key in multiple sources.

3 1. Manually specify the priority of a config source in a custom implementation.

See the Explanation.

30. Create a custom ConfigSource that reads from an in-memory map.

See the Explanation.

Page 4 of 10

31. Inject values from a custom ConfigSource into a bean.

See the Explanation.

32. Combine property values from multiple config sources.

See the Explanation.

33. Create a ConfigSourceProvider that registers multiple sources.

See the Explanation.

34. Override MicroProfile default config source ordinal in microprofile-config.properties.

See the Explanation.

35. Access a mapped config interface using ConfigProvider.

See the Explanation.

36. Build a test case to validate config mapping injection in Quarkus.

See the Explanation.

37. Build a reusable ConfigUtil class to fetch values dynamically.

See the Explanation.

38. Inject a profile-specific config property using @ConfigProperty.

See the Explanation.

39. Inject the active profile name at runtime.

See the Explanation.

40. Create different database configurations per environment.

See the Explanation.

Page 5 of 10

41. Use environment variable to set the profile.

See the Explanation.

42. Enable a Quarkus extension only for the dev profile.

See the Explanation.

43. Use @IfBuildProfile annotation to create a bean only in a specific profile.

See the Explanation.

44. Use @Profile to control bean registration in Spring-like fashion (Quarkus).

See the Explanation.

45. Create a REST endpoint that reports active profile and config source.

See the Explanation.

46. Add a timeout to a synchronous service method.

See the Explanation.

47. Configure a timeout duration via MicroProfile Config instead of annotation.

See the Explanation.

48. Create a REST endpoint using timeout protection.

See the Explanation.

49. Handle TimeoutException with a try-catch block.

See the Explanation.

50. Demonstrate async service method using @Asynchronous.

See the Explanation.

Page 6 of 10

51. Combine @Asynchronous and @Timeout for non-blocking protection.

See the Explanation.

52. Differentiate behavior: sync vs async method timeout.

See the Explanation.

53. Access fault tolerance config via MicroProfile Config programmatically.

See the Explanation.

54. Use a config profile to set different timeouts for environments.

See the Explanation.

55. Log timeout events for diagnostics.

See the Explanation.

56. Set timeout globally for all FT methods (default).

See the Explanation.

57. Configure FT globally for a specific bean using FQN.

See the Explanation.

58. Return fallback value manually when timeout occurs.

See the Explanation.

59. Demonstrate the thread behavior of sync timeout.

See the Explanation.

60. Test @Timeout with @Asynchronous and catch exception on CompletionStage.

See the Explanation.

Page 7 of 10

61. Document default timeout value behavior in the absence of annotation or config.

See the Explanation.

62. Configure retry delay between attempts.

See the Explanation.

63. Use MicroProfile Config to externalize retry settings.

See the Explanation.

64. Write a test that verifies retry behavior.

See the Explanation.

65. Log each retry attempt using a counter.

See the Explanation.

66. Use @Fallback to define a fallback method on failure.

See the Explanation.

67. Define fallback method with the same signature as the original.

See the Explanation.

68. Use fallback together with retry.

See the Explanation.

69. Use a fallback class instead of a method.

See the Explanation.

70. Customize CircuitBreaker parameters.

See the Explanation.

Page 8 of 10

71. Apply fallback with CircuitBreaker.

See the Explanation.

72. Use MicroProfile Config to customize CircuitBreaker.

See the Explanation.

73. Write a test that triggers the CircuitBreaker.

See the Explanation.

74. Check CircuitBreakerOpenException in fallback.

See the Explanation.

75. Manually reset the breaker state (only in tests/dev).

See the Explanation.

76. Log CircuitBreaker transitions with a wrapper method.

See the Explanation.

77. Chain @Retry, @Timeout, and @Fallback together.

See the Explanation.

78. Use @Bulkhead with an asynchronous method.

See the Explanation.

79. Write a test that exceeds bulkhead limits.

See the Explanation.

80. Log when bulkhead rejects new calls.

See the Explanation.

Page 9 of 10

81. Combine @Bulkhead and @Fallback to recover from concurrency saturation.

See the Explanation.

82. Configure bulkhead values using MicroProfile Config.

See the Explanation.

83. Differentiate behavior between sync and async bulkhead.

See the Explanation.

84. Use global fault tolerance configuration defaults.

See the Explanation.

85. Override global configuration with method-level annotation.

See the Explanation.

86. Simulate heavy load to observe bulkhead behavior.

See the Explanation.

87. Use ExecutionContext in fallback to detect BulkheadException.

See the Explanation.

88. Group fault tolerance settings by prefix for manageability.

See the Explanation.

89. Create reusable config profile for staging environment.

See the Explanation.

90. Dynamically read config fallback threshold from application.properties.

See the Explanation.

Page 10 of 10

91. Log circuit breaker and bulkhead metrics for monitoring.

See the Explanation.

92. Monitor bulkhead and circuit breaker states in real time.

See the Explanation.

93. Apply @Bulkhead to a JAX-RS endpoint to throttle API usage.

See the Explanation.

EX378 Red Hat Certified Cloud-native Developer exam Free Dumps

EX378 Red Hat Certified Cloud-native Developer exam Free Dumps

Share this post

Related Posts

EX248 Red Hat Certified Specialist in Enterprise Application Server Administration Exam Free Dumps

Red Hat Certified Engineer EX294 Dumps Questions

EX280 Red Hat Certified OpenShift Administrator exam Free Dumps

EX374 Red Hat Certified Specialist in Developing Automation with Ansible Automation Platform Exam Free Dumps

EX210 Red Hat Certified Specialist in Cloud Infrastructure Exam Free Dumps

EX200 RHCSA Red Hat Exam Training Material

Latest Red Hat EX447 Questions and Answers