Book Image

Oracle SOA Infrastructure Implementation Certification Handbook (1Z0-451)

By : Kathiravan Udayakumar
Book Image

Oracle SOA Infrastructure Implementation Certification Handbook (1Z0-451)

By: Kathiravan Udayakumar

Overview of this book

<p>Completing the Oracle SOA Infrastructure Implementation Certification develops your conceptual and real-world understanding of the primary components of the Oracle SOA Suite, including BPEL process engine and Oracle Service Bus and will allow you to become familiar with Service Oriented Architecture concepts.<br /><br /><br />This definitive certification guide provides a disciplined approach to be adopted for successfully clearing the 1Z0-451 Oracle SOA Foundation Practitioner exam to attain the Oracle SOA Infrastructure Implementation Certification.<br /><br />The book starts with essential SOA concepts and then dives into building of composite applications. You will then learn how to work with technology and application adapters. Next, you will learn orchestrating Services with BPEL and advanced BPEL concepts. Midway through the book you will learn about Mediator components and Human Workflows. The book will then cover Oracle Business Rules and securing services and composite applications. Towards the end of the book, you will learn how to monitor and manage SOA Deployment. The book concludes&nbsp; with a post assessment exam that will give you a feel for the actual SOA Foundation Practitioner exam, and a must-have developer reference that covers important SOA concepts.</p>
Table of Contents (22 chapters)
Oracle SOA Infrastructure Implementation Certification Handbook (1Z0-451)
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Pre-assessment Test
Post-assessment Test

Chapter 6


  1. 1. a: Multiple CatchAll blocks can be used in a BPEL.

  2. 2. b: Multiple CatchAll blocks cannot be used per BPEL scope. Only one CatchAll block is allowed per BPEL scope.

  3. 3. a: Fault management framework is the right option. Catch and CatchAll blocks can be used only with BPEL processes.

  4. 4. a: Custom Java actions are available to handle the faults through the fault management framework.

  5. 5. b: At the least, fault binding definitions are required to utilize the fault management framework.

  6. 6. a: Fault management policies take higher precedence over Catch and CatchAll faults. Fault policies can be defined to re-throw the faults back to the Catch activities.

  7. 7. b: We can have multiple different fault policies defined per SOA installation and they can be bound to required composites.

  8. 8. a: Fault management framework doesn't differentiate between a sync and an async process. As a best practice, it is advisable to have a retry option for a sync process.

  9. 9. a: Fault management framework doesn't differentiate between a sync and an async process. As a best practice, it is advisable to have a retry option for an async process.

  10. 10. b: Fault policies can be used to handle both custom as well as system-defined faults.

  11. 11. a: Multiple compensation handlers can be defined per BPEL through multiple scopes. However, this cannot be true per BPEL scope.

  12. 12. b: Multiple compensation handlers can be defined per BPEL through multiple scopes. However, this cannot be true per BPEL scope.

  13. 13. b: The property alias required for a message correlation ID is defined in the WSDL file.

  14. 14. a: Correlation sets are defined in the BPEL file.

  15. 15. b: getFaultAsString() can be used only in the CatchAll block. It cannot be used in the Catch block, and it doesn't return any results.