Microsoft 70-595 Value Pack (Frequently Bought Together)

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 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.SendPortName Exists. Set the filter for Send Port B to Error. ReceivePortName Exists.

A company uses BizTalk Server 2010 to receive electronic orders from multiple customers. You have schemas for all the order formats that the customers send. You need to create a business process that handles an incoming order. You create a canonical schema that represents an order. You also create an orchestration that handles an order of the canonical schema. What should you do next?

• A. Create maps from each of the customer order formats to the canonical schema. Create a receive port and location and bind the port to the orchestration. Use the maps on the receive port.
• B. Create maps from each of the customer order formats to the canonical schema. Create a send port and bind it to the orchestration. Use the maps on the send port.
• C. Create maps from the canonical schema to each of the customer order formats. Create a receive port and location and bind the port to the orchestration. Use the maps on the receive port.
• D. Create maps from the canonical schema to each of the customer order formats. Create a send port and bind it to the orchestration. Use the maps on the send port.

An existing BizTalk Server 2010 messaging solution for processing orders has a send port group that contains two send ports.
Send Port A is for Supplier A and Send Port B is for Supplier B.
Each supplier receives only one copy of each order message.
The order schema has a promoted property named OrderAmount that contains the total amount of the order.
The send port group subscribes to all messages where a promoted property OrderAmount exists.
The send ports do not have a filter defined. Messages with an order amount less than or equal to 1000 must be sent to Supplier A.
Messages with an order amount greater than 1000 must be sent to Supplier B.
Only a single message can be sent to either Supplier A or Supplier B.
You need to modify the solution to route each order message to either Supplier A or Supplier B.
What should you do?

• A. Set a filter on Send Port A to subscribe for messages where OrderAmount is <= 1000. Set a filter on Send Port B to subscribe for messages where OrderAmount is > 1000. Stop and start the send port group.
• B. Keep the existing filter condition on the send port group. Add a filter condition on the send port group to subscribe for messages where OrderAmount is <= 1000. Add a filter OR condition on the send port group to subscribe for messages where OrderAmount is > than 1000.
• C. Delete the existing filter condition on the send port group. Add a filter condition on the send port group to subscribe for messages where OrderAmount is <= 1000. Add a filter OR condition on the send port group to subscribe for messages where OrderAmount is > 1000.
• D. Set a filter on Send Port A to subscribe for messages where OrderAmount is <= 1000. Set a filter on Send Port B to subscribe for messages where OrderAmount is > 1000. Delete the send port group.

A BizTalk Server 2010 orchestration calls a Business Rules Engine policy. This policy evaluates test scores to determine whether a candidate passes or fails. The BizTalk solution and the policy are deployed. Business users have decided that the value of a passing score should be raised from 60% to 70%. You need to adjust the policy to reflect the modified rule parameter. What should you do?

• A. Open the policy in the Business Rules Composer. Create a new version of the policy and edit this version to reflect the changed parameter. Then publish the new version.
• B. Open the policy in the Business Rules Composer. Create a new version of the policy and edit this version to reflect the changed parameter. Then deploy the new version.
• C. Open the policy in the Business Rules Composer and create a different policy with a new name. Then copy the currently deployed version to the new policy and modify to reflect the changed parameter. Deploy the new policy.
• D. Create a new vocabulary in the Business Rules Composer. Add the new parameter to this vocabulary and then publish the vocabulary.

You use the BizTalk WCF Service Publishing Wizard to expose a BizTalk Server 2010 orchestration as a Microsoft Windows Communication Foundation (WCF) service. It is exposed with the WCF-BasicHttp binding and a corresponding receive location is created. The outcome of a recent IT audit has required the use of the WCF-WSHttp binding instead of WCF-BasicHttp. You need to fulfill the audit requirements.
What should you do?

• A. In the BizTalk Administration console, modify the receive location and select WCF-Custom. Configure the updated port with the endpoint address (URI) of the deployed WCF service. Change the binding type to wsHttpBinding.
• B. In the BizTalk Administration console, modify the receive location and select WCF-WSHttp. Configure the updated port with the endpoint address (URI) of the deployed WCF service.
• C. Use the WCF Service Publishing Wizard to republish the orchestration. Select WCF-WSHttp as the transport type.
• D. Use the WCF Service Publishing Wizard to republish the orchestration. Use the Metadata only endpoint (MEX) to publish the metadata for the previously created receive location.