Microsoft TS: Developing Business Process and Integration Solutions by Using Microsoft BizTalk Server 2010 Sample Questions:

1. You are developing a BizTalk Server 2010 solution that has two orchestrations, A and B, that exist in different projects. A message sent between the orchestrations has a promoted property named OrderID that can be used as a unique identifier for the message. The two projects must remain independent from each other. Updates are made to Orchestration B to ensure that the output message promotes the OrderID property when it publishes the message. You need to enable Orchestration A to send a message to Orchestration B and receive a message back when Orchestration B finishes. You create a correlation type on the OrderID property and a new correlation set in Orchestration A. What should you do next?

A) Reference the Orchestration A project from the Orchestration B project. Create a new correlation set in Orchestration B by using the correlation type. Set the Receive shape on Orchestration A to initialize the correlation set. Set the Send shape on Orchestration B to follow the correlation set.
B) Set the Send shape in Orchestration A to initialize the correlation set. Set the Receive shape in Orchestration A to follow the correlation set.
C) Reference the Orchestration A project from the Orchestration B project. Create a new correlation set in Orchestration B by using the correlation type. Set the Send shape on Orchestration A to initialize the correlation set. Set the Receive shape on Orchestration B to follow the correlation set.
D) Set the Receive shape in Orchestration A to initialize the correlation set. Set the Send shape in Orchestration A to follow the correlation set.

2. A BizTalk Server 2010 messaging-only solution is used to process XML messages. The pipelines used in the receive location and the send port contain the XML validator pipeline component. Routing for failed messages is enabled on both the receive port and the send port. When validation fails on the receive side, messages must be routed to Send Port A. When validation fails on the send side, messages must be routed to Send Port B. You need to create subscriptions for Send Port A and Send Port B. What should you do?

A) Set the filter for Send Port A to Error.SendPortName Exists. Set the filter for Send Port B to Error. ReceivePortName Exists.
B) Set the filter for Send Port A to BTS.ReceivePortName Exists. Set the filter for Send Port B to BTS. SPName Exists.
C) Set the filter for Send Port A to Error.ReceivePortName Exists. Set the filter for Send Port B to Error. SendPortName Exists.
D) Set the filter for Send Port A to Error.ErrorType == ReceivePort. Set the filter for Send Port B to Error. ErrorType == SendPort.

3. In a Microsoft Visual Studio solution, you include an existing shared BizTalk Server 2010 project that is used by more than one BizTalk application. You specify that the shared BizTalk project will be deployed to the same BizTalk application as the other BizTalk projects in the solution. During deployment of the BizTalk project from Visual Studio, you receive the following error: Failed to add resource(s). Resource(Type="System.BizTalk:BizTalkAssembly" -Luid="Contoso.SharedComponent, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c4b6d1ca34bb90c0") is already in store and is either associated with another application or with another type. You need to deploy the projects of the solution that reference the shared BizTalk project without errors. What should you do?

A) Open Configuration Manager and clear the Deploy check box for all BizTalk projects. Then build and deploy the solution.
B) Use the BizTalk Administration console to export the assemblies as a Microsoft Windows Installer (MSI) package for the BizTalk solution.
C) Open Configuration Manager and clear the Deploy check box for the shared BizTalk project. Then build and deploy the solution.
D) Use the BizTalk Administration console to import a copy of the MSI package of the shared component into every BizTalk application.

4. You are moving a BizTalk Server 2010 application from a development environment to a QA environment for the first time. You export a copy of the BizTalk application and include the bindings. When importing the Microsoft Windows Installer (MSI) file into the QA environment, you receive the following
error: Failed to update binding information. (mscorlib)Cannot update send port "LogContosoMessage".
(Microsoft.BizTalk.Deployment)The following items could not be matched up to hosts due to name and/or trust level mismatches:Item: 'FILE' Host: 'ContosoLogHost' Trust level: 'Untrusted' You need to ensure that the MSI file can be imported into the QA environment. Which artifacts should you create?

A) a host named ContosoLogHost, a host instance that uses the default host, and a FILE receive adapter handler that uses the ContosoLogHost host instance
B) a BizTalk application and a FILE send adapter handler that uses the default host
C) a BizTalk application and a FILE send port named LogContosoMessage that uses the default host
D) a host named ContosoLogHost, a host instance that uses the ContosoLogHost host, and a FILE send adapter handler that uses the ContosoLogHost host instance

5. A BizTalk Server 2010 orchestration consumes a Microsoft Windows Communication Foundation (WCF) service. A request-response call to the WCF service is made inside a non-transactional scope. The scope has an exception handler that has its Exception Object Type property set to the type of the fault operation returned from the service. The handler receives the fault message. The WCF service throws a typed fault exception named WidgetException. You need to extract the exceptions detail node from thefault message. What should you do in the WCF send port configuration?

A) Set the Propagate Fault Message option to True. Specify the source of the outbound WCF message body by selecting Template. In the XML expression box, enter the XML of the WidgetException message.
B) Set the Propagate Fault Message option to True. Specify the source of the inbound BizTalk message body by selecting Path and entering the XPath expression for the WidgetException node.
C) Set the Propagate Fault Message option to True. Specify the source of the inbound BizTalk message body by selecting Envelope (soap:Envelope).
D) Set the Propagate Fault Message option to True. Specify the source of the inbound WCF message body by selecting BizTalk Request Message Body.

Solutions: