Oracle Application Integration Architecture 11g Essentials v6.0 (1z0-543)

Page:    1 / 5   
Total 74 questions

Which two AIA artifacts will be deployed as SCA composites when considering the
Deployment Plan?

  • A. Enterprise Business Object
  • B. Composite Business Process
  • C. Enterprise Business Flow
  • D. Enterprise Business Message

Answer : B,C

Explanation: A composite is unit of deployment for SCA and contains service components.
The name of the composite is the same as the name of the Oracle Application Integration
Architecture (AIA) artifact.
The composites are created for the following AIA artifacts:
* Composite Business Process (B)
* Enterprise Business Flow (C)
* Enterprise Business Service
* Application Business Connector Service
* Utility Services
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack:

Composites -
Note #1: The SCA Assembly Model consists of a series of artifacts, which are defined by elements contained in XML files. A SCA runtime may have other non-standard representations of the artifacts represented by these XML files, and may allow for the configuration of systems to be modified dynamically. However, the XML files define the portable representation of the SCA artifacts.
The basic artifact is the Composite, which is the unit of deployment for SCA and which holds Services which can be accessed remotely.
Note#2:Service Component Architecture (SCA) is a software technology created by major software vendors including IBM and Oracle. SCA provides a model for composing applications that follow Service-Oriented Architecture principles.The technology encompasses a wide-range of disparate technologies and as such is specified in various independent specifications in order to maintain programming language and application environment neutrality.
Oracle SOA Suite uses the SCA(Service Component Architecture)standard as a way to assemble service components into a SOA composite application. SCA provides a programming model for the following:
* Creating service components written with a wide range of technologies, including programming languages such as Java, BPEL, C++, and declarative languages such as
XSLT. The use of specific programming languages and technologies (including web services) is not required with SCA.
* Assembling the service components into a SOA composite application. In the SCA environment, service components are the building blocks of applications

Which two statements are true about Enterprise Business Messages?

  • A. An EBM defines a specific message format for service requests and responses in EBS operations
  • B. An EBM represents the specific EBO content needed to perform a specific activity.
  • C. An EBM may contain details about more than one type of action like query and update, for example,in the same message.
  • D. An EBM implementation might be specified in a .bpel file.

Answer : A,B

Explanation: Any application invoking the Enterprise Business Services (EBSs) has to generate the EBM to pass the EBM as a payload to the EBS.
At the most basic level, EBMs (Enterprise Business Messages) are the messages that are exchanged between two applications. The EBM represents the specific content of an
EBO(Enterprise Business Object)needed for performing a specific activity.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack:
Designing and Constructing Enterprise Business Flows

Which two best describes a situation where AIA’s error handling framework is invoked?

  • A. At every BPEL receive activity whether or not an error has occurred
  • B. At every ESB service invocation
  • C. When a BPEL partner link experiences an invocation error
  • D. When a mediator service experiences an error

Answer : C,D

Explanation: There are two categories of faults:
1) Business faults
Business faults are generated when there is a problem with the information being processed. For example, a credit card number is invalid.
Error actions for business faults that are internal to BPEL are configured in catch blocks.
These are business faults that are thrown by a throw activity. Error notifications and logging for these business faults are handled by AIAAsyncErrorHandlingBPELProcess.
Error actions for business faults from external applications and services are configured using the Composite Fault Policy Framework. These are business errors that are returned by an invoked service or application when using a BPEL invoke activity. Error notifications and logging for these business faults are handled by
2) System faults
System faults occur as a result of problems within the running of the BPEL process or
Mediator service component. For example, data cannot be copied properly because the variable name is incorrect or because of transformation errors.
Error actions for system faults are configured using the Composite Fault Policy Framework.
Error notifications and logging for system faults are handled by
Note: The AIA Error Handling Framework provides the following key features for integration services operating in an AIA ecosystem.
* Unified Error Handling Approach
* Works across technologies, including BPEL and Mediator components, business-to- business (B2B), and ODI.
* Works across categories of faults, including business and system, run-time, and technical faults.
* Works across integration patterns.
* Adopts the Oracle SOA Suite 11g tech stack.

Which two AIA backends are used by AIA Harvester to store metadata about the implementation artifacts?

  • A. Lifecycle DB
  • B. OER
  • C. ODI
  • D. MDS

Answer : A,B

Explanation: Once you have unit-tested, source-controlled, and completed your composite implementation, you can harvest these design-time composites into the Project Lifecycle
Workspace and, optionally, Oracle Enterprise Repository(OER).
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack:
Harvesting Design-Time Composites into Project Lifecycle Workbench and Oracle

Enterprise Repository -

For which two reasons would you execute PIP Auditor reports regularly during your PIP development?

  • A. This is the compliance report for a given PIP, which gives you statistics based on category and priority.
  • B. The detailed violation report goes down to line/column level so that you can fix them easily.
  • C. This is the compliance report that shows CAVS test results.
  • D. This report shows progress of PIP development.

Answer : A,D

Explanation: A:The PIP Auditor generates what is called a "Technical Compliance
Report", reporting code violations based on rules, priority, category, project, and test suite.
D: The PIP Auditor is run against your BPEL and ESB code to check whether they follow the AIA methodology for coding conventions. The output is a static HTML report. Therefore, the results are a single snapshot of your code at the time it was run.The PIP Auditor can be run against Oracle out-of-the-box PIPs, against PIPs that you have customized, or against your custom code that follows AIA design and development guidelines. Thus, in some cases, you may want to run the report weekly to continously monitor your progress (or lack thereof) of coding compliancy.The PIP Auditor reports on compliancy to coding standards.The PIP Auditor also provides suggestions for fixes for each of the identified violations.


Which two statements are true about EBOs?

  • A. Each EBO has an EBS to expose the create, read, update, and delete operations as well as other supporting operations.
  • B. An EBO is composed of nonreusable data components.
  • C. EBOs serve as a common data abstraction across systems.
  • D. EBOs are application-specific representations of business entitles.

Answer : B,C

Explanation: EBOs (Enterprise Business Objects) have the following characteristics:
* They contain components that satisfy the requirements of business objects from the source and target application data models.
* EBOs differ from other data models in that they are not data repositories. (B)
Instead, they provide the structure for exchanging data. XML provides the vocabulary for expressing business data. The XML schema is an XSD file that contains the application- independent data structure to describe the common object. (C)
* Each EBO is represented in an XML schema (XSD) file format.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack,Introduction to EBOs

What are the two relationships between Service Solution Component definition for ABCS and the actual implementation performed In the Service Constructor/JDeveloper?

  • A. Service Solution Component of ABCS types have no relation to the eventual implementation in the Service Constructor/JDeveloper.
  • B. Service Solution Component of ABCS types are upstream of the eventual implementationinService Constructor/JDeveloper.
  • C. Service Solution Component provides functional metadata for the ABCS before the actual implementation in JDeveloper.
  • D. Service Solution Component provides the Interface for the ABCS before the actual Implement in JDeveloper.

Answer : B,C

Explanation: A service solution component is a chunk of functionality within the scope of a business task that is implemented as an AIA service artifact. For example, a service solution component corresponds to an Application Business Connector Service (ABCS),
Enterprise Business Service(EBS), or Enterprise Business Flow (EBF). A service solution component conveys the functionality that the AIA service artifact needs to fulfill.
Note #1:Define the service solution components that make up a business task in a Project
Lifecycle Workbench project. Each service solution component that you define should correspond to a single composite or service that will be built or reused. These composites and services collectively accomplish the functionality and logic required by their parent business task.
Note #2:Service Constructor guides the developer through four of the six subphases of developing an ABCS. The four subphases are:
* Define service description and details
Define high-level information about the service solution component and the project and business task to which it belongs.
* Define the service object (or interface)
Define the type of message that the ABCS will receive and if and how it will reply.
* Define the target service
Define the services that will be invoked by the ABCS, and the message it will pass to those services.
* Define additional options and generation point
Define options such as error-handling and extension run-time location, as well as the launching point to generate an Oracle JDeveloper project for continued development.
Once the developer has completed the Service Constructor interview, a complete Oracle
JDeveloper project is produced that the developer will continue to develop, incorporating use case-specific requirements.
Service Constructor enhances developer productivity by providing a more user-friendly interface to the Composite Generator (formerly the Artifact Generator) and auto-inspection of services and project selection from the Project Lifecycle Workbench.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack:
Working with Project Lifecycle Workbench Service Solution Components

When would you use security in AIA Integration flows?

  • A. between any two services
  • B. between remote invocations and as required by business
  • C. between all remote invocations
  • D. only between two Web service invocations

Answer : B

Explanation: Note: An Integration Flow represents the journey of a message from a business event-triggering source, through possible intermediary milestones, to one or more target milestones. At each milestone, the message is stored in a different state.
An Integration Flow represents the runtime path of a message. It is not a design-time artifact.
AIA recommends a variety of integration styles and patterns to enable the flight of a message in an Integration Flow. The AIA artifacts that are required for the collaboration between applications or functions are dependent on the integration style adopted for an Integration
Note 2: Oracle Application Integration Architecture (AIA) provides support for all security- related functions including:
* Identification
* Authentication (verification of identity)
* Authorization (access controls)
* Privacy (encryption)
* Integrity (message signing)
* Non-repudiation
* Logging
The service-oriented architecture (SOA)-based integration approach allows for clear separation between the interface and the actual business logic. This provides the
Security models:
* Point-to-Point or End-to-End Security
* Transport-Level Security
* Message-Level Security
* Securing ABCS
Reference: Oracle Application Integration Architecture, Infrastructure Components and

Utilities Guide -

Which two statements best describe how CAVS is important in AIA?

  • A. CAVS provides a unified error handling and logging solution to help enableuntegration issues.
  • B. CAVS can measure compliance of AIA artifacts against AIA guidelines.
  • C. CAVS can test single services and end-to-end flows involved in an integration scenario.
  • D. CAVS is a testing framework you can use to define, perform, and evaluate test invocations against any Web service.

Answer : C,D

Explanation: The Composite Application Validation System (CAVS) is a framework that provides a structured approach to test integration of Oracle Application Integration
Architecture (AIA) services. The CAVS includes test initiators that simulate web service invocations and simulators that simulate service endpoints.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack:
Introduction to the Composite Application Validation System

Which two operations can AIA Deployment Plan perform?

  • A. Update AIA artifacts to SOA MDS
  • B. Create an SOA domain on Oracle Weblogic server
  • C. Create an SOAserver connection configuration
  • D. Deploy an ADF application

Answer : A,C

Explanation: A:AIA Deployment Plan Generator utility helps generate Deployment Plans for extended artifacts and AIA Installation Driver (AID) helps deploy them.
Note: A deployment plan is an auto generated xml file that
will be composed of services selected for deployment (by the individual performing the deployment), along with the necessary configurations and dependant artifacts.
Note 2: AIA Installation Driver (AID) is responsible for deploying the content defined in the deployment plan to the target servers defined in AIAInstallProperties.xml. The installation driver is a command line tool that can interpret line by line of the deployment plan and deploys it to the specified target server.

One of your clients wants to migrate to AIA 11g environment from existing AIA 2.5 implementations. Which statements are true about the environment migration?
* Foundation Pack 2.5 can be directly upgrade AIA Foundation pack 11g R1
** Oracle 11g database is required
*** AIA Foundation Pack 11g R1 is a new installation
A. *and**
B. ***
C. **and***
D. *,**, and***

Answer : B R1 platform, Release 1.

Reference: Oracle Fusion Middleware Migration Guide for Oracle Application Integration
Preparing to Migrate AIA Artifacts to AIA 11g Release 1

Which two are standard elements in the EBM header?

  • A. WerbCode
  • B. EBOName
  • C. DateTime
  • D. GUID

Answer : A,B

Explanation: EBM Header Components:VerbCode, EBOName,EBMID, RequestEBMID,
CreationDateTimeand MessageProcessingInstruction.
Note: The EBM header is an integral part of every EBM. You can consider the EBM header as a wrapper or an envelope around transactional data messages. It comprises representations of functional data such as Document Identification, Involved Parties
(Sender, Provider, intermediary services, Security, and Transaction Rules [Transaction
State and Exceptions]).
The EBM header provides the ability to:
* Carry information that associates the message with the originator.
* Uniquely identify the message for auditing, logging, security, and error handling.
* Associate the message with the specific instance of the sender system that resulted in the origination of the document.
* Store environment-specific or system-specific information.
The requirements pertaining to infrastructure-related services such as auditing, logging, error handling, and security necessitate the introduction of additional attributes to the message header section of the EBM.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack:

Introducing EBM Header Concepts -

What message exchange pattern will require you to explicitly correlate the request and the response in an EBF?

  • A. Fire-and-forget pattern
  • B. Subscribe pattern
  • C. Synchronous request-response
  • D. Asynchronous request-delayed response pattern

Answer : D

Explanation: A) If the control is to be blocked until a response is returned to the point of invocation, choose EBF Request-Reply pattern. This would be a synchronous call.
B)If after the EBF is invoked the triggering point does not wait for the response and continues on, this invocation of the EBF would be an asynchronous call.
Check whether the processing of the EBF results in a response.
Is there a need to correlate the request and the response?
If the answer is yes, this is a case of delayed response. Use the EBF request-delayed response pattern. If the answer is no, then choose the EBF fire-and-forget pattern.
C) Any EBF operation invoked because of a subscription to a publish event should use the
EBS subscribe pattern.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack:
To identify the message exchange pattern (MEP) for an EBF

What optional component is AIA designed to interact with?

  • A. Oracle Identity Manager
  • B. Oracle Enterprise Repository
  • C. Oracle Enterprise Manager
  • D. Oracle Virtual Directory

Answer : B

Explanation: Oracle Application Integration Architecture (AIA) leverages Oracle Enterprise
Repository as its SOA repository solution, providing a centrally managed user interface for discovering and learning about the SOA assets in your Oracle AIA ecosystem.
Specifically, all prebuilt AIA design-time interfaces, including Enterprise Business Service
(EBS) WSDL files, Application Business Connector Service (ABCS) WSDL files, Enterprise
Business Object (EBO) XSD files, Enterprise Business Message (EBM) XSD files, and their underlying artifacts, relationships, and metadata are delivered via Oracle Enterprise
Beyond this, you also can publish run-time, deployed composites into Oracle Enterprise
Repository. As such, Oracle Enterprise Repository can provide visibility and coverage across the span of the SOA design-time and run-time lifecycles.
Note: Once you have unit-tested, source-controlled, and completed your composite implementation, you can harvest these design-time composites into the Project Lifecycle
Workspace and, optionally, Oracle Enterprise Repository.
When you choose to harvest into Oracle Enterprise Repository, annotations on Application
Business Connector Service (ABCS) WSDL files, Enterprise Business Service (EBS)
WSDL files, Enterprise Business Object (EBO) XSD files, and Enterprise Business
Message (EBM) XSD files are published to Oracle Enterprise Repository. Harvesting to
Oracle Enterprise Repository is optional.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack:
Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository

Which two statements best describe situations when you should favor implementing an
ABCS as a BPEL process?

  • A. The requirement involves simple transformation and invocation.
  • B. The interaction with the external system is stateless.
  • C. Multiple invocations to external applications are required to accomplish the integration.
  • D. Content augmentation or validation cannot be done using XSLT.

Answer : C,D

Explanation: Oracle AIA provides two blueprints for implementing an ABCS: Oracle
Mediator and BPEL.
BPEL is used when the ABCS must augment content, validate content, or both. In most situations, the ABCS must have a conversation with one or more participating applications to enrich the content. It may also have to handle state management. (not B)
In this scenario, BPEL is the preferred technology. BPEL enables you to perform the tasks listed previously and also enables you to extend the connector.
The Oracle Mediator blueprint can be applied in situations in which you do not need the
ABCS to do additional enrichment and validation of the content. In this model, the ABCS are implemented as Mediator services.
Note: The role of the ABCS (Application Business Connector Services) is to expose the business functions provided by the participating application in a representation that is agreeable to a service interface.
Note 2: The ABCS can be implemented in two ways:
* The first approach is to make complete use of components that are built using Oracle
Fusion Middleware technologies to make up the ABCS.
The service is implemented as a Mediator service or a BPEL process.
* The second approach is to build the transformation services, to a large extent, as part of the participating application.
This approach can be taken when the participating application's technology stack has the infrastructure to perform the transformations. However, a lightweight ABCS still must perform the translations related to cross-reference details.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle
Application Integration Architecture Foundation Pack:

Implementing ABCS -

Page:    1 / 5   
Total 74 questions