You are developing an application in BizTalk Server 2010 to synchronize data. An orchestration contains a request-response port that sends a message to a web service on the destination system. At the end of the calendar year, all the rows of the source tables are updated. This process causes update delays for the destination system. You need to create a BizTalk Administration console hub query to find out which orchestrations are waiting for their updates to complete and have not encountered an error.
Which query expressions should you specify?

• A. Search For Equals Messages and Message Status Equals Suspended
• B. Search For Equals Suspended Service Instances and Instance Status Equals Suspended (Not Resumable)
• C. Search For Equals Running Service Instances and Instance Status Equals Dehydrated
• D. Search For Equals Suspended Service Instances and Instance Status Equals Suspended (Resumable)

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

A BizTalk Server 2010 messaging solution processes XML messages. The solution uses a single Business Activity Monitoring (BAM) activity and BAM tracking profile to extract content values from the message. Some of the values are bound to a receive port when the message is received. The other values are bound to a send port when the message is transmitted. At run time you find out that instead of one, two records are created in the BAM database for each processed message. One record contains only the values bound to the receive port. The second record contains only the values bound to the send port. You need to ensure that only one record is created that contains all the values for every message.
What should you do?

• A. Add a document reference URL to the tracking profile.
• B. Add a continuation and continuation ID to the tracking profile.
• C. Add a relationship to the tracking profile.
• D. In the tracking profile, associate a unique value from the message payload to the ActivityID field.

A BizTalk Server 2010 application contains an orchestration with one receive port and one send port.
You evaluate the runtime behavior of the orchestration by viewing the promoted properties of any inbound and outbound messages of the orchestration. You need to modify the application so that you can view these promoted properties on the BizTalk Server Group Hub page. What should you do?

• A. In the BizTalk Administration console, modify the orchestration properties. Under Track Message Properties, select the check boxes for incoming and outgoing messages.
• B. In Orchestration Designer, change the Type Modifier property to Public. Redeploy the orchestration.
• C. In the BizTalk Administration console, modify the orchestration properties. Under Track Message Bodies, select Before orchestration processing and After orchestration processing.
• D. In Orchestration Designer, change the Report To Analyst property to True. Redeploy the orchestration. Create filters on the receive port receive location that evaluate the messages promoted properties.