Online Access Free 070-595 Exam Questions

A BizTalk Server 2010 orchestration consumes a Microsoft Windows Communication Foundation (WCF) service. A request-response call to the WCF service is made inside a non-transactional scope. The scope has an exception handler that has its Exception Object Type property set to the type of the fault operation returned from the service. The handler receives the fault message. The WCF service throws a typed fault exception named WidgetException. You need to extract the exceptions detail node from thefault message. What should you do in the WCF send port configuration?

• A.Set the Propagate Fault Message option to True. Specify the source of the inbound BizTalk message body by selecting Path and entering the XPath expression for the WidgetException node.
• B.Set the Propagate Fault Message option to True. Specify the source of the inbound WCF message body by selecting BizTalk Request Message Body.
• C.Set the Propagate Fault Message option to True. Specify the source of the inbound BizTalk message body by selecting Envelope (soap:Envelope).
• D.Set the Propagate Fault Message option to True. Specify the source of the outbound WCF message body by selecting Template. In the XML expression box, enter the XML of the WidgetException message.

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.Use the WCF Service Publishing Wizard to republish the orchestration. Select WCF-WSHttp as the transport type.
• C.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.
• D.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.

A supplier sends messages that they sign with a certificate to a BizTalk Server 2010 application. You need to ensure that the received messages are signed with the certificate. What should you do?

• A.Use the XMLTransmit pipeline.
• B.Use a custom pipeline that leverages the MIME/SMIME decoder component.
• C.Use a custom pipeline that leverages the MIME/SMIME encoder component.
• D.Use the XMLReceive pipeline.

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 Microsoft Windows Installer (MSI) file for the EDI application and include the party information.
• B.Create a binding file for one of the assemblies in the EDI application.
• C.Create a binding file for the EDI application and include the party information.
• D.Create a binding file that contains the binding for the BizTalk group.

You are developing a BizTalk Server 2010 orchestration that consumes a web service located at http:// localhost/ProcessData.asmx. The orchestration contains a non-transactional scope with an exception handler that handles any SOAP exceptions returned from the web service. The orchestration then completes successfully. After the orchestration completes with exceptions, you notice that the original messages posted to the web service are suspended in the BizTalk Administration console. You need to ensure that the messages are not suspended but are saved in an archive file on a shared server.
What should you do?

• A.In the Administration console, change the send pipeline to PassThruTransmit and enable Ordered delivery in the transport options.
• B.In Orchestration Designer, modify the SOAP exception handler to send a copy of the original message to a new send port that will transmit the message as a file.
• C.In the Administration console, modify the SOAP send port and enable routing for failed messages. Create a FILE send port with filters ErrorReport.ErrorType==FailedMessage and ErrorReport. OutboundTransportLocation==http://localhost/ProcessData.asmx.
• D.In Orchestration Designer, set Delivery Notification to Transmitted on the request/response port that sends the SOAP message. Create an exception handler with exception type DeliveryFailureException. In the handler, send a copy of the original message to a new send port that will transmit the message as a file.