Due to popular demand, here are some answers to the questions.
Well, not answers exactly ... just some pointers to the get you in the right direction...
1. Are there advantages to building workflows using only XAML? Are there disadvantages?
See Keith Elder's blog on "Leveraging Workflow Foundation", particularly the section on storing workflow definitions in the database.
Also, see Matt Miler's Templates for Windows Workflow XAML activation projects
2. What are the pros and cons of using an ExternalDataExchange service versus going directly to the WorkflowQueuingService?
Sam Gentile: Windows Workflow 102
3. When are attached dependency properties useful in WF programming?
See: Dependency Property Notes
4. What behavior does the default scheduling service provide?
Hosting Windows Workflow
5. How can my code participate in a database transaction with a workflow instance?
Advanced Workflow: Workflows and Transactions
6. Why would I use a tracking service?
Follow the links in Tomas Restporo's WF Tracking Services Explained.
7. Describe a scenario where the WF runtime will cancel an executing activity.
I'd be looking to hear, for example, what happens inside a Listen activity. Also, see Matt W's Implementing the M of N Pattern in WF
8. Describe a scenario where I'd need to spawn a new ActivityExecutionContext.
Matt Milner: ActivityExecutionContext in WF.
9. Tell me why I'd use a compensation handler.
Guy Burstein explains the essence: Compensating and Fault Handling.
10. Tell me about the following activities: Replicator, Parallel, and Policy.
Advanced Workflow: Replicator Tips and Tricks
Kirk Allen Evans: Understanding ParallelActivity in WF
Sahil: Composite Activities in WF.
WF: Rules and Conditions
