S90-04 practice question 15 of 35
Which of the following types of information are generally documented as part of a service profile?
Full set: 100 questionsA service profile is a collection of metadata that provides a comprehensive, non-technical definition of a service. It is a key artifact in SOA governance used for discovery, management, and assessment. This profile generally includes governance-related information such as the policies that apply to the service (e.g., security, SLA), its current delivery or lifecycle status (e.g., in development, active, deprecated), and the designated custodian or owner responsible for its maintenance and evolution. This information is essential for managing the service as a formal IT asset within an enterprise service portfolio.
B. service compositions the service participates in: This describes the service's runtime usage and consumer relationships, which are external to the service's intrinsic definition and are typically tracked separately in a service registry or dependency map.
1. Erl, T., et al. (2009). SOA Governance: Governing Shared Services and SOA. Prentice Hall.
Chapter 6, "Putting SOA Governance into Practice," Section "Service Information and Metrics," details the essential metadata to be captured for each service. This includes "Service Owner" (Custodian), "Service Status" (Delivery Status), and "Associated Policies," directly supporting options A, C, and D.
2. Erl, T. (2007). SOA: Principles of Service Design. Prentice Hall.
Chapter 6, "Service Contracts (Standardization and Design)," explains that a service contract consists of both technical and non-technical parts. The non-technical portion includes metadata such as policies and service-level agreements, which are documented as part of the service's official profile.
3. Josuttis, N. M. (2007). SOA in Practice: The Art of Distributed System Design. O'Reilly Media.
Chapter 4, "SOA and the Organization," Section "Service Portfolio Management," discusses the necessity of maintaining a central inventory of services. The information stored for each service includes its owner, lifecycle state, and associated non-functional requirements like policies, aligning with options A, C, and D. The text distinguishes this definitional data from runtime dependencies like compositions.
Keep practicing
Take the free S90-04 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other S90-04 practice questions
- Question 1When collecting information for the purpose of defining business logic for potential serv…
- Question 2Which of the following statements describe business process steps that are not suitable f…
- Question 3Which of the following is an expected deliverable of successfully completing the service-…
- Question 4The top-down approach is not recommended when:
- Question 5Which of the following is not a valid reason for defining service composition candidates …
- Question 6Which of the following is not a common role on an SOA project?
