Joe McKendrick, ebizQ's SOA in Action Blogger, is a nationally published author and consultant
with deep knowledge and insights regarding trends and developments in
the technology industry. He is a contributing editor to a number of
national and international publications and Websites including
Database Trends & Applications, ZDNet, and Webservices.Org. He also
serves as analyst for Evans Data Corp., and is lead analyst for Evans'
Web services and enterprise development management issues surveys.
SOA in Action Blog
|
« Governance in Action -- If Duplication is What the Business Wants, Then... | Main | Five Activities of Highly Effective SOA Deployments » June 10, 2008Who Wants to be an SOA Guru? Take This Challenging Quiz We all know what we need to know about SOA, and learn more every day (especially if you visit the ebizQ site on a daily basis, right?). But how much do you know about some of the inner workings of SOA? Or the history of some of the standards and practices? ebizQ has created a challenging quiz to test your SOA acumen. In 10 tough multiple choice questions, you will find out where you fall on the SOA IQ continuum. For example, how acquainted are you with the origins of SOAP and XML, or the essential commands of REST? Score an 8 out of 10 or above, and you'll rate a place in the "SOA Boardroom"! Take the quiz here. _____________________________________________________________________ Posted by joemckendrick in SOA | Digg This | Add to del.icio.us Trackback Pings TrackBack URL for this entry: Web Services, XML, SOAP, UDDI do not an SOA make. This quiz is about Web Services, not SOA. :-( Posted by: John at June 11, 2008 04:03 AM I should have 10 of 10! Buhhh!!! What does it mean when a service is "stateless?" You said: None of the above The correct answer is: The service does not depend on the condition of any other service; all information needed to provide a response comes from the request I don't agree. I think this answer the question about "autonomous", not stateless. Stateless services need all state information from the caller. Statefull service like long running processes need correlation id to act on the state, while a stateless service don't do correlation to anything. Give me back my last point, I want to be a SOA master ;) Posted by: Casper at June 13, 2008 04:25 PM Post a comment
|
