SOA S90.09 Prüfungsfragen : SOA Design & Architecture Lab

Ein Nichtbestehen der S90.09 Prüfung bedeutet nicht nur verlorene Zeit, sondern auch eine erneute Anmeldegebühr. Die 40 Übungsfragen zu SOA Design & Architecture Lab auf PrüfungFrage helfen Ihnen, dieses Risiko von vornherein deutlich zu senken.

SOA S90.09 Prüfungsübersicht:

Zertifizierungsanbieter:	IBM
Prüfungsname:	Praktische Prüfung zu SOA-Design und -Architektur S90.09
Prüfungsnummer:	S90.09
Prüfungsformat:	Praktische Prüfung im Laborformat, Szenariobasierte Aufgaben, Praktische Durchführung von Architekturentwürfen
Verwandte Zertifizierungen:	IBM SOA Associate IBM Certified SOA Solution Designer
Verfügbare Sprachen:	Englisch
Beispielfragen:
Prüfungsmethode:	Praktische, szenariobasierte Prüfung (üblicherweise mit Aufgaben zum Entwurf und zur Gestaltung von Architekturen)
Voraussetzungen:	Vorkenntnisse zu SOA-Konzepten, unternehmensweiter Integration sowie eine entsprechende Schulung zur IBM SOA-Architektur oder verwandte Zertifizierungen werden empfohlen.

SOA S90.09 Prüfungsthemen:

Antworten auf häufig gestellte Fragen zur S90.09 Prüfung

SOA Design & Architecture Lab S90.09 Prüfungsfragen mit Lösungen

Frage #1

Service Consumer A sends a message with a business document to Service A (1), which
writes the business document to Database A (2). Service A then forwards the business
document to Service B (3), which writes the business document to Database B (4).
Service B then responds to Service A with a message containing a failure or success code
(5) after which Service A responds to Service Consumer A with a message containing a
failure or success code (6). Upon receiving the message, Service Consumer A updates a
log table in Database B (7). The log entry is comprised of the entire business document.
Database A is dedicated to the Service A service architecture and Database B is a shared
database.

You are told that the database updates performed by Service A and Service B must be
either both successful or they cannot happen at all. The database update performed by
Service Consumer A must happen after it is given the outcome of the database updates
performed by Service A and Service B . Given that Service Consumer A must also update
Database B as part of this service composition architecture, how is it possible to fulfill these
requirements?

A. The Service Data Replication pattern can be applied to Service Consumer A and
Service B so that separate dedicated databases can be established allowing Service
Consumer A to make updates independently of Service B . Service A is simply redesigned
to not write the business document to Database A until after it receives a message
containing a success code from Service B.
B. The State Repository pattern can be applied so that Service A writes the business
document data to a separate state database until it receives a response message from
Service B . If the response message contains a success code, Service A writes the
business document to Database A.
If the response contains a failure code, Service A
discards the data that was written to the state database.
C. None of the above.
D. The Atomic Service Transaction pattern can be applied to encompass Service A,
Service B and Service Consumer A.
This will guarantee that all of the actions performed by the service composition participants will either be successful or will be rolled back if anyone
is not successful.

Frage #2

Our service inventory contains the following three services that provide invoice-related data
access capabilities: Invoice, InvProc, and Proclnv. These services were created at different
times by different project teams and were not required to comply to any design standards.
Therefore each of these services has a different data model for representing invoice data.
Currently each of these three services has one service consumer: Service Consumer A
accesses the Invoice service(1). Service Consumer B (2) accesses the InvProc service,
and Service Consumer C (3) accesses the Proclnv service. Each service consumer
invokes a data access capability of an invoice-related service, requiring that service to
interact with the shared accounting database that is used by all invoice-related services (4,
5, 6).
Additionally, Service Consumer D was designed to access invoice data from the shared
accounting database directly (7). (Within the context of this architecture. Service Consumer
D is labeled as a service consumer because it is accessing a resource that is related to the
illustrated service architectures.)

A project team recently proclaimed that it has successfully applied the Contract
Centralization pattern to the service inventory in which the Invoice service, InvProc service,
and ProcInv service reside. Upon reviewing the previously described architecture you have
doubts that this is true. After voicing your doubts to a manager, you are asked to provide
specific evidence as to why the Contract Centralization is not currently fully applied. Which
of the following statements provides this evidence?

A. The Contract Centralization pattern is not fully applied because none of the invoice-
related services are carrying out data access logic via a centralized and standardized
invoice service. This is primarily because the Standardized Service Contract principle was
not consistently applied during the delivery processes of the individual services.
B. The Contract Centralization pattern is not fully applied to the Invoice, InvProc, and
ProcInv services because they are being accessed by different service consumers and
because they have redundant logic that introduces denormalization into the service
inventory.
C. The Contract Centralization pattern is not fully applied because Service Consumer D is
accessing the shared accounting database directly.
D. None of the above.

Frage #3

Service Consumer A sends a message to Service A.
There are currently three duplicate implementations of Service A (Implementation 1, Implementation 2, Implementation 3).
The message sent by Service Consumer A is intercepted by Service Agent A (1), which
determines at runtime which implementation of Service A to forward the message to.
All three implementations of Service A reside on the same physical server.

You are told that after Service A was deployed, each of its three implementations was
claimed by a different IT department, which means each implementation of Service A has a
different owner. You are informed that a new service capability will soon need to be added
to Service A . This service capability will introduce new business logic specific to Service A
as well as logic required to access a shared database. What steps can be taken to ensure
that the service owners will each add the service capability in a consistent manner to their
respective implementations of Service A?

A. The Standardized Service Contract principle is applied to ensure that the new service
capability is consistently added to the service contract of each implementation and that it
extends the existing Service A service contract in a manner that is compliant with current
design standards. The Service Loose Coupling principle is applied to ensure that the new
service capability remains decoupled from the underlying logic and implementation so that
Service Consumer A does not become indirectly coupled to any new logic or to the shared
database.
B. The Legacy Wrapper pattern can be applied to establish a new wrapper utility service
that will provide standardized data access service capabilities for the shared database.
This will avoid Service A from having to access the shared database directly and will further
support the application of the Service Loose Coupling principle between Service A and the
new utility service. By abstracting the data access logic into the wrapper service, there is
no need to add the new service capability to each implementation of Service A .
C. None of the above.
D. The Contract Centralization pattern can be applied so that when the new service
capability is added, the Service A service contract will become the primary contact point for
Service A . This will avoid Service Consumer A or any other potential service consumer
from being designed to access the shared database directly. The Service Abstraction
principle can be applied to further hide the implementation details so that Service
Consumer A and other service consumers are unaware of the fact that the shared
database is being accessed.

Frage #4

A. The Asynchronous Queuing pattern can be applied to establish a messaging queue
between Service Consumer A and Service A so that Service Consumer A does not need to
remain stateful while it waits for a response from Service A .
B. The Service Statelessness principle can be applied together with the State Repository
pattern in order to establish a state database that Component A can defer the business
document data to while it waits for a response from Component B.
The Service Autonomy principle can be applied together with the Service Data Replication pattern to establish a
dedicated replicated database for Component B to access instead of the shared Database
C. None of the above.
D. The Service Statelessness principle can be applied together with the State Repository
pattern in order to establish a state database that Component A can defer the business
document data to while it waits for a response from Component B.
The Service Autonomy principle can be applied together with Service Abstraction principle, the Legacy Wrapper
pattern, and the Service Facade pattern in order to isolate Database A so that it is
encapsulated by a separate wrapper utility service and to hide the Database A
implementation from Service A and to position a Facade component between Component
B and the new wrapper service. This Facade component will be responsible for
compensating the unpredictable behavior of Database A.
E. The Service Statelessness principle can be applied together with the State Repository
pattern in order to extend Database C so that it also becomes a state database allowing
Component A to temporarily defer the business document data while it waits for a response
from Component B.
The Service Autonomy principle is applied together with the Legacy
Wrapper pattern to isolate Database A so that it is encapsulated by a separate wrapper
utility service. The Compensating Service Transaction pattern is applied so that if the
response time of Service A exceeds 30 seconds, a notification is sent to a human
administrator to raise awareness of the fact that the eventual response of Service A will be
rejected by Service Consumer A.

Fragen und Antworten: