S90-04 practice question 6 of 35

Which of the following is not a common role on an SOA project?

Full set: 100 questions
Answer options
A: service custodian
B: schema custodian
C: policy custodian
D: silo custodian Correct answer
Correct Answer:
D. silo custodian
Explanation

Service custodian, schema custodian, and policy custodian are all formally recognized and common roles within an SOA governance framework. Each is responsible for the lifecycle management and quality of a specific type of asset: a service, a data schema, or a policy, respectively. The role of a "silo custodian" is not a recognized SOA role. In fact, it is conceptually contradictory to the primary goals of SOA, which include breaking down application and data silos to promote interoperability and information sharing across the enterprise. The objective is to eliminate silos, not to assign a custodian to maintain them.

Why Incorrect

A. service custodian: This is a fundamental role in SOA, responsible for the design, development, and ongoing maintenance of a specific business service throughout its lifecycle.
B. schema custodian: This is a critical data governance role responsible for managing and ensuring the quality and standardization of data models and schemas used by services.
C. policy custodian: This is a key governance role responsible for defining, managing, and enforcing the policies that govern the design, development, and usage of services.

References

1. Erl, T., et al. (2009). SOA Governance: Governing Shared Services and SOA. Prentice Hall.

Page 178, Section 7.2.3, "Policy Custodian": This section explicitly defines the Policy Custodian role and its responsibilities.

Page 180, Section 7.2.5, "Service Custodian": This section details the responsibilities of the Service Custodian.

Page 181, Section 7.2.6, "Schema Custodian": This section defines the Schema Custodian role. The term "silo custodian" is not mentioned as a formal role; instead, the book consistently discusses SOA as a means to overcome the problems caused by information silos.

2. Erl, T. (2007). SOA: Principles of Service Design. Prentice Hall.

Page 40, Section 3.2, "Goals and Benefits of Service-Oriented Computing": This section explains that a primary goal of SOA is to break down "application silos" to achieve enterprise-wide interoperability, reinforcing that a "silo custodian" role would be counter-intuitive to the paradigm.

Scroll to Top