S90-04 practice question 31 of 35

Which of the following are considered best practices for measuring the compliance of a service with its expected quality of service levels during the service testing phase?

Full set: 100 questions
Answer options
A: The supporting infrastructure should be tested to determine thresholds and other limitations. Correct answer
B: Services should be tested individually and as part of service compositions. Correct answer
C: The service being tested should be called at a rate which is greater than or equal to its expected rate of call. Correct answer
D: Statistics collected during the service testing phase should be documented in the service profile.
Correct Answer:
A. The supporting infrastructure should be tested to determine thresholds and other limitations.; B. Services should be tested individually and as part of service compositions.; C. The service being tested should be called at a rate which is greater than or equal to its expected rate of call.
Explanation

Best practices for measuring Quality of Service (QoS) compliance during testing involve a comprehensive approach. This includes stress and load testing the underlying infrastructure to understand its capacity and limitations (A), which directly impact service performance. It is also crucial to test services both individually and as part of compositions (B), as integration can introduce latency and contention, affecting overall QoS. Finally, to validate performance metrics like response time and throughput defined in the service-level agreement (SLA), the service must be subjected to realistic and peak loads by calling it at a rate greater than or equal to its expected usage (C).

Why Incorrect

D. The service profile, as part of the service contract, documents the required or promised QoS levels. Test results are documented in test reports, which are then compared against the service profile to determine compliance.

References

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

Page 496, Section 17.4, "Contract-Driven Testing": This section emphasizes testing services against the policies and QoS capabilities defined in their contracts. This supports testing at expected loads (C) and testing compositions (B) to ensure the aggregated QoS is met.

Page 497, "Performance Testing" and "Stress Testing": The text explicitly describes the need to "simulate the anticipated production message load" and to "overload the service with messages" to discover its limitations, directly supporting options (C) and (A).

2. Erl, T., et al. (2009). SOA Design Patterns. Prentice Hall.

Page 121, "Service Level Agreement" Pattern: Discusses that SLAs define measurable QoS characteristics. The process of verifying these characteristics inherently requires the testing practices described in A, B, and C. The pattern states, "The terms of the SLA need to be constantly monitored and governed," and the initial verification of this happens during the testing phase.

3. Papazoglou, M. P. (2012). Web Services & SOA: Principles and Technology (2nd ed.). Pearson.

Chapter 12, Section 12.5, "Testing Web Services": This chapter details the necessity of testing services not just for functionality but also for non-functional requirements like performance and reliability. It describes load testing (testing under expected and peak loads) and testing services within a composite application, which aligns with options (A), (B), and (C).

Scroll to Top