This is a Part 5 of the Questions for interview articles.
Part 1: BizTalk: Questions for interview without answers
Part 2: BizTalk: Interview questions and principles
Part 3: WCF: Questions for studying and interview
Part 4: WCF: Questions for studying and interview: Discovery
Part 5: WCF: Questions for studying and interview: Routing Service
WCF, Routing Service
Q&A
What are the features of the Routing Service (RS): Protocol bridging; Message transformation; Content-based routing; Application pools; Dynamic configuration; SOAP processing; Service hosting; Error handling; Backup endpoints?
Which routing scenarios can RS implement: Service aggregation; Interface recomposition; Service versioning; Service chain; Priority routing?
Is it possible to modify the routing configuration at run time?
What is the RS doing if there is no match for a message routing?
Can we route to the mix of the one-way and two-way destination endpoints using a single service endpoint?
Do we have to create the implementation of the RS as a .NET class or an .svc file with “Service=”System.ServiceModel.Routing.RoutingService, ” plus a configuration file is enough?
What is it a SOAP processing? How it works?
Can it convert messages between Soap 1.1/Soap 1.2/Soap 2.0 and/or WS-Addressing August 2004/WS-Addressing 1.0?
What is it a Backup endpoint?
What is the maximum number of the Backup endpoints?
What is it a Protocol bridging?
What is it a Content-based routing?
How the Priority routing is working?
How we can host the RS?
Are there limits on using streaming for the RS? Where we have to buffer the messages?
How we can expose mex endpoints of the original services through the RS?
Can we use the RS as a load balancer?