SOA Project Delivery & Methodology Set 1

1.

Top-down approaches typically ____________ the long-term governance burden of services.

increase decrease eliminate None of the above.

2.

Two service delivery projects are being carried out concurrently. Each project has its own project team.
Even though both projects are delivering services for the same service inventory, each project team is given complete independence as to how services are designed and developed and what design standards are to be used. Which of the following statements describes a likely consequence of this approach?

The service inventory will be comprised of services that comply to different design standards and these
services will therefore not be compatible or interoperable. Services with redundant and overlapping logic may be delivered because no effort was made tocoordinate the delivery of the services between the two projects. One project team may decide to follow a top-down delivery approach, whereas the other project teammay follow a bottom-up delivery approach. All of the above.

3.

The primary deliverable of the service inventory analysis is a ____________ of the service inventory.

blueprint contract composition architecture legend

4.

The Inventory Management System project is delivering a modest solution comprised of three services. The project team is following a bottom-up approach whereby service developers are building the services to
fulfill tactical (short-term) requirements. Although not everyone agrees with this approach, it does actually directly support the following service-oriented computing goal:

Increased Intrinsic Interoperability Increased Business and Technology Alignment Increased Federation None of the above.

5.

Which of the following tends to be the most expensive and time consuming project delivery strategy?

bottom-up top-down meet-in-the-middle round-about

6.

SOA projects introduce new considerations that tend to augment the traditional project lifecycle as follows:

they tend to introduce the need for more up-front analysis effort they tend to require closer collaboration between business and technology experts they tend to require a careful prioritization of tactical (short-term) and strategic (long-term) requirements they tend to introduce new project roles

7.

A service candidate is:

a conceptual service a proposed service that may not yet physically exist a modeled service produced via a service modeling process a modeled service that initially acts as the starting point for the physical design of the service

8.

Bottom-up delivery is generally focused on fulfilling ____________ requirements while top-down delivery is generally focused on fulfilling ____________ requirements.

tactical (short-term), tactical (short-term) strategic (long-term), strategic (long-term) tactical (short-term), strategic (long-term) strategic (long-term), tactical (short-term)

9.

Which of the following statements makes sense?

The bottom-up approach is tactical (short-term) and therefore advocates that up-front analysis effort be
carried out before the service inventory blueprint is finalized. The top-down approach is tactical (short-term) and therefore advocates that up-front analysis effort becarried out before the service inventory blueprint is finalized. The bottom-up approach is strategic (long-term) and therefore advocates that up-front analysis effort becarried out before the service inventory blueprint is finalized. The top-down approach is strategic (long-term) and therefore advocates that up-front analysis effort becarried out before the service inventory blueprint is finalized.

10.

Which of the following statements is true?

The meet-in-the-middle delivery approach allows an on-going top-down analysis to occur while services
are designed and delivered. The only requirement is that delivered services eventually be updated to be
kept in alignment with the results of the top-down analysis. The meet-in-the-middle delivery approach is essentially based on the bottom-up approach in that itallows services to be delivered without up-front analysis. The only difference is that the meet-in- the-
middle approach advocates the use of object-orientation principles instead of service- orientation
principles. The meet-in-the-middle delivery approach is essentially based on the top-down approach in that itallows services to be delivered after the completion of the top-down analysis. The only difference is that
the meet-in-the-middle approach advocates the use of people that act as mediators who ensure that
business analysts and technology architects can collaborate harmoniously. None of these statements are true.

SOA Project Delivery & Methodology Set 1

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Congratulations

COMPANY

Products

OTHERS

Partner

SOA Project Delivery & Methodology Set 1

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Answer & Solution

Answer: Option B

Solution:

Congratulations

Detail Form

COMPANY

Products

OTHERS

Partner