About this previous year paper
SERVICE ORIENTED ARCHITECTURE (KDS079) – COMPLETE SOLVED PAPER
Time: 3 Hours Max Marks: 100
Instructions: Attempt all Sections
SECTION A (2 × 10 = 20 Marks)
Attempt all questions in brief
a) Total latency with 5 SOAP services Each service = 150 ms
Total base latency = 5 × 150 = 750 ms Orchestration overhead = 10% of 750 = 75 ms
Total latency = 825 ms
b) WSDL vs SOAP vs UDDI
| Standard | Purpose |
|---|---|
| WSDL | Service description |
| SOAP | Message exchange protocol |
| UDDI | Service registry |
c) Allowable downtime (99.9% availability) Total hours/year = 365 × 24 = 8760 hrs
Downtime = 0.1% of 8760 = 8.76 hours/year
d) Design process of client services in SOA Identify service requirements
Define service contract Implement service interface
Test interoperability Deploy and monitor
e) Technologies for service integration SOAP / REST
ESB (Enterprise Service Bus) APIs
Message queues Middleware
f) Total latency with orchestration overhead
5 services × 150 ms = 750 ms Orchestration overhead = 20 ms
Total latency = 770 ms
g) Payback period calculation Implementation cost = $1.5 million
Annual savings = $0.5 million
Payback Period=1.50.5=3 years\text{Payback Period} = \frac{1.5}{0.5} = \mathbf{3 \text{ years}}Payback Period=0.51.5=3 years
h) Role of SOA in Big Data analytics Enables modular data services
Improves scalability Simplifies integration of analytics tools
Supports real-time processing
i) Best practices for SOA strategy Loose coupling
Reusable services Strong governance
Security policies Version control
j) Defect reduction calculation Initial defects = 10% of 10,000 = 1000
New defects = 2% of 10,000 = 200
Defects reduced = 800
SECTION B (10 × 3 = 30 Marks)
Attempt any three
a) Evolution of SOA and MSA
SOA: Enterprise-level integration, ESB-centric MSA: Lightweight, independently deployable services
Drivers: Scalability, agility, DevOps, cloud computing
b) Composite applications & latency calculation Service latencies: 120 ms + 100 ms + 80 ms
Total latency = 300 ms
Composite applications combine multiple services to deliver business functionality.
c) Strategic architecture governance
Governance defines policies for: Service design
Security Versioning
It reduces downtime by ensuring standardization and proactive monitoring.
d) Future trends in Big Data + SOA Event-driven SOA
Cloud-native services AI-powered orchestration
Real-time analytics Impact: Faster insights, better scalability
e) Governance best practices Clear service ownership
Policy enforcement SLA monitoring
Compliance auditing Ensures regulatory and operational compliance.
SECTION C (10 × 5 = 50 Marks)
Attempt one from each question
Q3(a) Challenges in adopting SOA in legacy systems
Challenges: Tight coupling
Old technologies High migration cost
Solutions: Wrappers
API gateways Phased migration
Financial impact: Reduced long-term maintenance and operational costs
Q3(b) Why MSA is preferred over SOA
| Aspect | SOA | MSA |
|---|---|---|
| Fault isolation | Medium | High |
| Deployment | Centralized | Independent |
| Scalability | Moderate | Excellent |
Q4(a) Methodology for SOA development
Steps: Service identification
Service design Implementation
Testing Deployment
Iterative development allows faster feedback and reduced logistics failures.
Q4(b) Principles of service design
Loose coupling Statelessness
Reusability Result: Improved scalability and maintainability
Q5(a) Governance framework for retail system
Includes: Policy management
SLA enforcement Security standards
Service lifecycle management
Q5(b) Technologies enabling SOA
Web services REST APIs
ESB Message brokers
Used to integrate legacy mainframes with modern apps.
Q6(a) Big Data orchestration gain calculation
Processing = 1 TB/day Yearly data = 365 TB
20% speed improvement = 73 TB equivalent gain/year
Q6(b) Big Data characteristics
Volume Velocity
Variety Veracity
SOA helps handle these via modular and scalable services.
Q7(a) Framework aligning business & SOA
Business process modeling Service mapping
SLA definition Continuous monitoring
Ensures scalability and agility.
Q7(b) SOA improving IT efficiency (case study)
Reusable services reduce development by 30% Downtime reduced by 40%
Maintenance cost lowered by 25%