You are integrating BizTalk Server 2010 with a secure Microsoft Windows Communication Foundation (WCF) service that does not have metadata exchange (MEX) enabled. The web service provider distributes an XML schema with a root node named SecretData without a namespace for the data provided by the web service. You generate a BizTalk schema based on the XML schema. You finish developing the application and deploy it for integration testing. When testing the service, you trace the messages received from the service. You see that the response message is within a single element named SecureResponse. SOAP elements wrap the response message and the SecureResponse element. You need to specify the inbound message body properties to ensure that the message can be received. What should you do?

• A. Choose the Path option. For the body path expression, specify /*[local-name()='SecureResponse']/* [local-name()='SecretData'].
• B. Choose the Path option. For the body path expression, specify /*[local-name()='SecretData']. Add the soapProcessing endpoint behavior with the property processMessages=True.
• C. Choose the Body option. Add the useRequestHeadersForMetadataAddress service behavior.
• D. Choose the Envelope option. Add the soapProcessing endpoint behavior with the property processMessages=True.

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 host named ContosoLogHost, a host instance that uses the default host, and a FILE receive adapter handler that uses the ContosoLogHost host instance
• C. a BizTalk application and a FILE send port named LogContosoMessage that uses the default host
• D. a BizTalk application and a FILE send adapter handler that uses the default host

You are configuring a BizTalk Server 2010 environment with one server running Microsoft SQL Server for the BizTalk databases and Enterprise Single Sign-On (SSO) store. There are two BizTalk servers. All software has been installed. Both BizTalk servers will share a BizTalk group. You need to complete the installation in this environment. You start the BizTalk Server Configuration wizard on both BizTalk servers.
What should you do next?

• A. On BizTalk Server 1, select Custom Configuration. Create a new SSO system and BizTalk group on the server running SQL Server. On BizTalk Server 2, select Custom Configuration. Join the existing SSO system and BizTalk group.
• B. On BizTalk Server 1, select Custom Configuration. Create a new SSO system and BizTalk group on the server running SQL Server. On BizTalk Server 2, select Custom Configuration. Create a new SSO system and BizTalk group on the server running SQL Server.
• C. On BizTalk Server 1, select Custom Configuration. Create a new SSO system and BizTalk group on the server running SQL Server. On BizTalk Server 2, select and apply Basic Configuration.
• D. On BizTalk Server 1, select and apply Basic Configuration. On BizTalk Server 2, select and apply Basic Configuration.

A BizTalk Server 2010 solution receives invoices in XML format. The solution receives only two types of files: XML files that contain only a single invoice.
The filename of these files starts with the letter S.XML files that contain multiple invoices. The filename of these files starts with the letter M.
You create a receive port with two FILE receive locations. Both receive locations point to the same folder on the file system but each receive location has a different file mask. You configure each receive location to pick up one type of invoice XML. You need to ensure that the single-invoice XML files are processed as soon as possible, and the multiple-invoice XML files are only processed outside of office hours. What should you do?

• A. Set the service window of the receive location that picks up the multiple-invoice XML files to reflect the outside office hour time range. Make sure this receive location is disabled.
• B. Set the schedule start date and stop date of the receive location that picks up the multiple-invoice XML files to reflect the outside office hour time range.
• C. Set the service window of the receive location that picks up the multiple-invoice XML files to reflect the outside office hour time range. Enable both receive locations.
• D. In the receive port, delete one of the receive locations. Configure the other receive location to pick up both types of files. Set the service window to reflect the outside office hour time range.