Microsoft 70-595 Value Pack (Frequently Bought Together)

A BizTalk Server 2010 solution contains multiple applications. One of the applications sends EDI messages to trading partners. The trading partners are defined as parties in the BizTalk Administration console. You need to extract the binding and party information for only the EDI application in an XML file so that you can store that information in source code control. What should you do?

• A. Create a binding file for one of the assemblies in the EDI application.
• B. Create a binding file for the EDI application and include the party information.
• C. Create a Microsoft Windows Installer (MSI) file for the EDI application and include the party information.
• D. Create a binding file that contains the binding for the BizTalk group.

A BizTalk Server 2010 solution uses an orchestration to send XML documents to various vendors. The XML documents are delivered by an FTP port. The port is configured in the orchestration with the Binding property set to Specify later. You need to ensure that the FTP address of the send port can be specified in the orchestration at run time. What should you do?

• A. Configure the Binding property for the port in the orchestration to Direct. Set the value of the Microsoft. XLANGs.Core.PortBinding property for this port in the orchestration to the appropriate vendor address.
• B. Configure the Binding property for the port in the orchestration to Specify now. Bind the orchestration to this new port. Set the value of the Microsoft.XLANGs.BaseTypes.Address property for this port in the orchestration to the appropriate vendor address.
• C. Create a new send port group. Add a new FTP send port to the send port group for each vendor. Bind the orchestration to this send port group.
• D. Configure the Binding property for the port in the orchestration to Dynamic. Set the value of the Microsoft.XLANGs.BaseTypes.Address property for this port in the orchestration to the appropriate vendor address.

You are developing a BizTalk Server 2010 map. The input schema contains multiple orders in one message. Each order has an Amount field. The output schema contains records named FulfillmentItem with a Price element. Only those orders with an amount greater than 1000 should map to the output schema. You need to add logic to the map to filter out any orders that have an amount less than or equal to 1000. What should you do?

• A. Drag a Value Mapping functoid onto the map. Connect the first input of the functoid to the Amount field in the order schema and connect the record node of the order schema to the second input. Connect the output of the functoid to the FulfillmentItem record node of the output schema.
• B. Drag a Greater Than functoid onto the map. Connect the first input of the functoid to the Amount field in the order schema and assign a value of 1000 in the second input. Connect the output of the functoid to the FulfillmentItem record node of the output schema.
• C. Drag a Less Than functoid onto the map. Connect the first input of the functoid to the Amount field in the order schema and assign a value of 1000 in the second input. Connect the output of the functoid to the FulfillmentItem record node of the output schema.
• D. Drag a Greater Than functoid onto the map. Connect the first input of the functoid to the Amount field in the order schema and assign a value of 1000 in the second input. Connect the output of the functoid to the Price element of the FulfillmentItem record node of the output schema.

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.

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.ErrorType == ReceivePort. Set the filter for Send Port B to Error. ErrorType == SendPort.
• B. Set the filter for Send Port A to Error.SendPortName Exists. Set the filter for Send Port B to Error. ReceivePortName 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 BTS.ReceivePortName Exists. Set the filter for Send Port B to BTS. SPName Exists.