S90-04 practice question 27 of 35

Which accurately describe the relationship between a service profile and a service registry record?

Full set: 100 questions
Answer options
A: Service registry record is the name used to distinguish a service profile once its associated service is deployed.
B: The service profile and the service registry record are always the same document.
C: Service profiles and service registry records can contain similar types of information. However, their formats are often different because the service registry record format is usually dependent upon the specific service registry product being used. Correct answer
D: A service registry record often contains a subset of the information found in a service profile due to the application of the Service Abstraction principle.
Correct Answer:
C. Service profiles and service registry records can contain similar types of information. However, their formats are often different because the service registry record format is usually dependent upon the specific service registry product being used.
Explanation

A service profile is a design-time artifact that contains a comprehensive description of a service. A service registry record is a runtime artifact that contains information necessary for service discovery and invocation. While the information in a registry record is often derived from the service profile, they are distinct. The format and schema of the service registry record are dictated by the specific registry product or technology (e.g., UDDI, ebXML, custom database), which often differs from the format of the design-time service profile. Therefore, they can contain similar information but typically have different formats.

Why Incorrect

A. A service registry record is a distinct data structure within a registry, not merely a different name for a service profile after deployment.
B. They are fundamentally different artifacts; a service profile is a design document, whereas a registry record is a runtime directory entry. They are not the same document.
D. While a registry record might contain a subset of the profile's information, the primary reason for the difference in format and structure is the registry's technology, not the Service Abstraction principle itself.

References

1. Erl, T. (2008). SOA: Principles of Service Design. Prentice Hall.

Page 108, Section 5.6 (Service Registry): "The format of the information stored in a service registry can vary. Some registries are based on specifications, such as UDDI or ebXML, that dictate a specific data model. Others are custom-built and implement a proprietary format." This supports the idea that the registry record format is dependent on the product.

Page 488, Section 16.4.3 (SOA Governance Controls): Discusses how service registries store "published service contracts and profiles," indicating they are related but distinct entities managed by the governance system. The profile is the source, and the registry record is the published runtime entry.

2. Josuttis, N. M. (2007). SOA in Practice: The Art of Distributed System Design. O'Reilly Media.

Chapter 5, The Service Registry, Page 103: "A registry contains a description of the available services... The description usually contains the technical contract (WSDL), the address of the service (endpoint), and some metadata..." This describes the content of a registry record. The book contrasts this with the broader design artifacts, confirming they are separate but related. The specific format (e.g., UDDI tModels, bindingTemplates) is shown to be technology-dependent.

Scroll to Top