SOA S90.09

SOA Design & Architecture Labは業界で広く認知されている認定資格であり、取得者のスキルの証明として高く評価されています。Jpshikenが提供するS90.09練習問題40問は、出題範囲を踏まえて専門家が作成した実践的な内容です。

SOA S90.09 試験概要:

SOA S90.09 試験シラバストピック:

SOA Design & Architecture Labの疑問を解決！よくある質問まとめ

S90.09とはどのような試験ですか？

S90.09試験は、「SOA Certification」認定を取得するための試験です。認定レベルはプロフェッショナルに位置づけられています。関連する認定にはCertified SOA Architect、SOA デザイン＆アーキテクチャ (S90.03)、上級 SOA デザイン＆アーキテクチャ (S90.08)、基礎 SOA ＆サービス指向コンピューティング (S90.01)、SOA テクノロジーコンセプト (S90.02)などがあり、キャリアパスに合わせた学習計画を立てやすい資格体系となっています。Jpshikenでは、この試験に対応した40問の練習問題を用意しています。

S90.09試験の問題数と試験時間はどれくらいですか？

S90.09試験の問題数は40、試験時間は60 分となっています。問題数を試験時間で割ると1問あたりに使える時間は意外と短く、読み込みに時間のかかる長文問題では特にペース配分が重要です。Jpshikenのテストエンジンには制限時間つきの模擬試験モードがあるため、本番と同じ時間設定で40問の練習問題を解きながら、時間切れを防ぐ解答リズムを身につけられます。

S90.09試験の合格点と受験料はいくらですか？

S90.09試験の合格基準点は70%、受験料はUSD $250です。万が一不合格になった場合、再受験には再度全額の受験料が必要になるため、本番前に十分な得点力があるか確認しておくことが大切です。Jpshikenの模擬試験で繰り返し自己採点し、安定して合格基準を上回る状態になってから受験を申し込むことをおすすめします。

S90.09試験に受験資格はありますか？

S90.09試験の受験条件について、公式情報では次のように案内されています。S90.01、S90.02、S90.03 および S90.08 の修了、またはそれと同等の SOA デザイン＆アーキテクチャに関する知識を有することを推奨します。。受験条件は変更される場合があるため、お申し込みの前に公式ページで最新の要件をご確認ください。

購入前にS90.09練習問題を試すことはできますか？

はい、Jpshikenでは無料サンプルをご用意しており、購入前に問題の傾向や解説の構成をご確認いただけます。また、ご購入後は365日間の無料更新サービスが付いているため、試験内容の改訂にも追加費用なしで対応できます。更新期間の終了後も、継続更新を50%割引でご利用いただけます。

万が一S90.09試験に合格できなかった場合はどうなりますか？

Jpshikenでは返金保証をご用意しています。ご購入後60日以内に対応する試験を受験し、不合格だった場合は、受験票の写しと公式スコアレポートのPDFを試験日から2日以内にご提出いただければ、7日以内に全額返金の手続きを行います。なお、ご購入後3日以内の受験、ダウンロード後に実際に受験されなかった場合、無料資料や期限切れのご注文は対象外となり、受験者名とご購入者名が一致している必要があります。返金の代わりに、同等の試験対策資料2つを無料でお受け取りいただき、元の製品の更新サービスを継続することも可能です。製品はお支払い後すぐにダウンロードでき、1分以内にメールでもお届けします。2時間経っても届かない場合はカスタマーサポートまでご連絡ください。インストールできるパソコンの台数に制限はありません。

S90.09試験ではどのようなトピックが出題されますか？

S90.09試験の出題範囲は、公式シラバスで3つの領域に分かれています。主な領域には、SOA・サービス・マイクロサービスによるデザインとアーキテクチャ（30%）、SOA デザイン＆アーキテクチャ ラボ（30%）、上級 SOA デザイン＆アーキテクチャ（40%）などがあります。各領域の詳細なトピックと配点は、このページ上部の試験大綱セクションに掲載していますので、あわせてご確認ください。

SOA Design & Architecture Lab 認定 S90.09 試験問題：

問題 #1

Service A sends a message to Service B (1). After Service B writes the message contents
to Database A (2) it issues a response message back to Service A (3). Service A then
sends a message to Service C (4). Upon receiving this message, Service C sends a
message to Service D (5), which then writes the message contents to Database B (6) and
issues a response message back to Service C (7).
Service A and Service D are in Service Inventory A.
Service B and Service C are in Service Inventory B.

You are told that in this service composition architecture, all four services are exchanging
invoice-related data in an XML format. However, the services in Service Inventory A are
standardized to use a different XML schema for invoice data than the services in Service
Inventory B.
Also, Database A can only accept data in the Comma Separated Value (CSV)
format and therefore cannot accept XML formatted data. Database B only accepts XML
formatted data. However, it is a legacy database that uses a proprietary XML schema to
represent invoice data that is different from the XML schema used by services in Service
Inventory A or Service Inventory B.
What steps can be taken to enable the planned data exchange between these four services?

A. None of the above.
B. The Data Model Transformation pattern can be applied so that data model
transformation logic is positioned between Service A and Service B, between Service C
and Service D, and between the Service D logic and Database B.
The Data Format Transformation pattern can be applied so that data format transformation logic is positioned
between Service A and Service C, and between the Service B logic and Database A.
C. The Data Model Transformation pattern can be applied so that data model
transformation logic is positioned between the Service B logic and Database A.
The Data Format Transformation pattern can be applied so that data format transformation logic is
positioned between Service A and Service B, between Service A and Service C, between
Service C and Service D, and between the Service D logic and Database B.
D. The Data Model Transformation pattern can be applied so that data model
transformation logic is positioned between Service A and Service B, between Service A
and Service C, between Service C and Service D, and between the Service D logic and
Database B.
The Data Format Transformation pattern can be applied so that data format
transformation logic is positioned between the Service B logic and Database A.

問題 #2

Service Consumer A sends Service A a message containing a business document (1). The
business document is received by Component A, which keeps the business document in
memory and forwards a copy to Component B (3). Component B first writes portions of the
business document to Database A (4).
Component B writes the entire business document to Database B and then uses some of
the data values from the business document as query parameters to retrieve new data from
Database B (5).
Next, Component B returns the new data back to Component A (6), which merges it
together with the original business document it has been keeping in memory and then
writes the combined data to Database C (7). The Service A service capability invoked by
Service Consumer A requires a synchronous request-response data exchange. Therefore,
based on the outcome of the last database update, Service A returns a message with a
success or failure code back to Service Consumer A (8).
Databases A and B are shared and Database C is dedicated to the Service A service
architecture.

There are several problems with this architecture: First, the response time of Database A is
often poor, resulting in Component B taking too much time to provide a response to
Component A.
This results in Component A consuming too many runtime resources while it
holds the business document in memory and it also causes unreasonable delays in
responding to Service Consumer A.
Additionally, Database B is being replaced with a different database product that supports a proprietary file format. This will disable the
current interaction between Component B and the new Database B.
What steps can be taken to solve these problems?

A. The State Repository pattern is applied so that Component A can defer the business
document data to a state database while it waits for a response from Component B.
The Asynchronous Queuing pattern can be applied so that a messaging queue is established
between Service Consumer A and Service A, thereby guaranteeing delivery and avoiding
Service Consumer A from being tied up too long waiting for Service A to respond. Finally,
the Data Format Transformation pattern can be applied to enable Component B to convert
to and from the new proprietary file format introduced by the database product that is
replacing Database B.
B. None of the above.
C. The Legacy Wrapper pattern is applied so that Database B is wrapped in a standardized
contract. This will establish a new wrapper utility service that will allow Database B to be
replaced with a different database product without affecting Service A . The Data Format
Transformation pattern can be applied within the new wrapper utility service to enable it to
convert to and from the new proprietary file format. The Service Data Replication pattern is
applied so that Component B can interact with a database that is replicated from the
shared Database B, regardless of what database product is used to replace Database B.
The Service Abstraction principle can be further applied to hide the implementation details,
including the changes mentioned in this solution, from Service Consumer A.
D. The State Repository pattern is applied so that Component A can defer the business
document data to a state database while it waits for a response from Component B.
The Service Data Replication pattern is applied so that Component B can interact with a
database that is replicated from the shared Database A.
This will improve performance and reliability that will affect both Component A and Service Consumer A.
Finally, the Legacy Wrapper pattern is applied so that Database B is wrapped in a standardized contract. This
will establish a new wrapper utility service that will allow Database B to be replaced with a
different database product without affecting Service A . Furthermore, the Data Format
Transformation pattern can be applied within the new wrapper utility service to enable it to
convert to and from the new proprietary file format.

問題 #3

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.

There are two problems with this service composition architecture that you are asked to
address: First, both Service Consumer A and Service B need to transform the business
document data from an XML format to a proprietary Comma Separated Value (CSV) in
order to write the data to Database B.
This has led to redundant data format transformation logic that has been difficult to keep in synch when Database B changes. Secondly, Service
A is an entity service that is being reused by several other service compositions. It has
lately developed reliability problems that have caused the service to become unavailable
for extended periods. What steps can be taken to solve these problems?

A. The service composition can be redesigned with the application of the Contract
Centralization pattern so that instead of writing the business document to Database B,
Service Consumer A sends the business document to Service B instead. This way, Service
B would provide the only location where data format transformation logic for Database B
needs to be carried out, which further supports the application of the Service Reusability
principle. The Reliable Messaging pattern can be applied so that acknowledgements are
passed between Service Consumer A and Service A and between Service A and Service B
. The Service Composability principle can be further applied to Service A in order to
optimize its service architecture for improved participation in multiple service compositions.
B. The Legacy Wrapper pattern can be applied so that data access to Database B is
separated into a new wrapper utility service. This way, the Data Format Transformation
pattern only needs to be applied within the logic of this new service which will expose a
standardized contract that both Service Consumer A and Service B can access. The
Asynchronous Queuing pattern can be applied so that messaging queues are established
between Service Consumer A and Service A and between Service A and Service B . The
Service Autonomy principle can be further applied to Service A in order to establish a more
isolated and reliable surrounding infrastructure.
C. The Legacy Wrapper pattern can be applied so that data access to Database B is
separated into a new wrapper utility service. This way, the Data Format Transformation
pattern only needs to be applied within the logic of this new service which will expose a
standardized contract that both Service Consumer A and Service B can access. The
Reliable Messaging pattern can be applied so that acknowledgements are passed between
Service Consumer A and Service A and between Service A and Service B . The Service
Composability principle can be further applied to Service A in order to optimize its service
architecture for improved participation in multiple service compositions.
D. None of the above.

問題 #4

Service A is an entity service with a functional context dedicated to invoice-related
processing. Service B is a utility service that provides generic data access to a database.
In this service composition architecture, Service Consumer A sends a SOAP message
containing an invoice XML document to Service A(1). Service A then sends the invoice
XML document to Service B (2), which then writes the invoice document to a database.
The data model used by Service Consumer A to represent the invoice document is based
on XML Schema A.
The service contract of Service A is designed to accept invoice documents based on XML Schema B.
The service contract for Service B is designed to accept invoice documents based on XML Schema A.
The database to which Service B needs to write the invoice record only accepts entire business documents in Comma
Separated Value (CSV) format.

Due to the incompatibility of the XML schemas used by the services, the sending of the
invoice document from Service Consumer A through to Service B cannot be accomplished
using the services as they currently exist. Assuming that the Contract Centralization pattern
is being applied and that the Logic Centralization is not being applied, what steps can be
taken to enable the sending of the invoice document from Service Consumer A to the
database without adding logic that will increase the runtime performance requirements of
the service composition?

A. Service Consumer A can be redesigned to write the invoice document directly to the
database. This reduces performance requirements by avoiding the involvement of Service
A and Service B . It further supports the application of the Service Abstraction principle by
ensuring that Service Consumer A hides the details of the data access logic required to
write to the database.
B. None of the above.
C. The service composition can be redesigned so that Service Consumer A sends the
invoice document directly to Service B.
Because Service Consumer A and Service B use XML Schema A, the need for transformation logic is avoided. This naturally applies the
Service Loose Coupling principle because Service Consumer A is not required to send the
invoice document in a format that is compliant with the database used by Service B.
D. Service Consumer A can be redesigned to use XML Schema B so that the SOAP
message it sends is compliant with the service contract of Service A . The Data Model
Transformation pattern can then be applied to transform the SOAP message sent by
Service A so that it conforms to the XML Schema A used by Service B.
The Standardized Service Contract principle must then be applied to Service B and Service Consumer A so
that the invoice XML document is optimized to avoid unnecessary validation.

解説：