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 ContosoLogHost host, and a FILE send 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 default host, and a FILE receive adapter handler that uses the ContosoLogHost host instance

A BizTalk Server 2010 solution contains an orchestration that sends messages through a logical port with the Binding property set to Specify later. You need to change the orchestration so that the logical port is not bound to a physical port. What should you do?

• A. Change the Binding property of the port to Specify now.
• B. Set the Type Modifier property of the port type to Public.
• C. Change the Binding property of the port to Direct.
• D. Set the Type Modifier property of the port type to Private.

You are developing a BizTalk Server 2010 orchestration that processes messages received from the BizTalk FILE adapter. You need to retrieve the original file name of the message and store it in a variable named FileName for future processing. What should you do?

• A. Inside an expression shape in the BizTalk Orchestration Designer, use the FILE.ReceivedFileName context property to assign the FileName variable.
• B. Inside an expression shape in the BizTalk Orchestration Designer, use the LEGACY.FilePath context property to assign the FileName variable.
• C. Inside a message assignment shape in the BizTalk Orchestration Designer, use the BTS.MessageType context property to assign the FileName variable.
• D. Inside a message assignment shape in the BizTalk Orchestration Designer, use the WSS.Filename context property to assign the FileName variable.

A BizTalk Server 2010 solution contains a map that transforms an internal order format into the order format of a supplier. You have examples of the internal order. You need to perform unit testing to make sure that the map works. You add a test project and a test class to the solution. You then add a reference to the project with the map. What should you do next?

• A. Add a reference to Microsoft.XLANGs.BaseTypes and to Microsoft.BizTalk.BaseFunctoids. Use the TestableSchemaBase class to test the schema.
• B. Add a reference to Microsoft.BizTalk.TestTools and to Microsoft.XLANGs.BaseTypes. Use the TestableMapBase class to test the map.
• C. Add a reference to Microsoft.XLANGs.BaseTypes and to Microsoft.BizTalk.BaseFunctoids. Use the TestableMapBase class to test the map.
• D. Add a reference to Microsoft.BizTalk.TestTools and to Microsoft.BizTalk.BaseFunctoids. Use the TestableMapBase class to test the map.

A BizTalk Server 2010 solution uses an orchestration to call an external Microsoft .NET assembly. The class on the assembly is not serializable. The Expression shape used to call the .NET assembly is contained within a scope that has its Transaction Type property set to Atomic. The call to the .NET assembly occasionally results in an exception being thrown. You need to handle the exception when it is thrown. Create a new scope with the Transaction Type property set to Long Running. What should you do next?

• A. Add an exception handler to the new scope. Drag and drop the atomic scope below the new scope.
• B. Add a compensation block to the atomic scope. Drag and drop the atomic scope inside the new scope.
• C. Add an exception handler to the new scope. Drag and drop the atomic scope above the new scope.
• D. Add an exception handler to the new scope. Drag and drop the atomic scope inside the new scope.