The amount of services participating in a service activity, the duration of the service activity, the amount of service activity instances that concurrently exist, and rules associated with the…

Question

Options

• Adesign-time data that is defined via the WSDL data definition language
• Bruntime data that is expressed as part of a WSDL service operation definition
• Cstate or context data that can be managed using WS-Coordination
• Drepository resource data that can be managed using WS-Policy via persistence in a database for

• B
  5% (2)
• C
  93% (41)
• D
  2% (1)

Explanation

Option C is correct because WS-Coordination is specifically designed to manage state and context data during service activities - it tracks dynamic runtime properties like participant count, activity duration, concurrent instances, and coordination rules governing how those services interact.

Why the distractors are wrong:

• A is wrong because WSDL is a design-time description language for service interfaces and message structures - it doesn't capture runtime participation or concurrency.
• B is wrong because while WSDL does describe service operations, those definitions describe the interface contract (inputs/outputs/faults), not live activity state like duration or concurrent instance counts.
• D is wrong because WS-Policy governs capability and requirement policies (e.g., security or QoS constraints), not coordination state - and it has no inherent database persistence mechanism.

Memory tip: Link WS-Coordination to the word "context" - it manages the coordination context that tracks the "who, how long, how many, and under what rules" of an active service transaction, much like a traffic controller tracking live vehicle flow rather than road design blueprints.

No community discussion yet for this question.