Configuring a Messaging Architecture

1. You have two Send Ports, both of which wish to subscribe to all the Order messages from the ERP system. What should you do?

   1. Create two Receive Locations in one Receive Port and make both Receive Locations receive orders from the ERP system. Create one Send Port and make the Send Port subscribe to all orders.

   2. Create two Receive Ports with one Receive Location in each and make both Receive Locations receive orders from the ERP system. Create one Send Port and make the Send Port subscribe to all orders.

   3. Create one Send Port. Configure transport options for one of the destinations and backup transport for the other destination. Set the filter to BTS.MessageType == Order.

   4. Create one Receive Port with one Receive Location in it and make the location receive orders from the ERP system. Create a Send Port Group. Make the Group subscribe to orders. Create two Send Ports and add the Send Ports to the Group.

2. You need to send invoices to a partner using the FTP Adapter. The partner has requested a special XML format that differs in structure from the canonical invoice format that you use in your Application. What should you do (choose all that apply)?

   1. Use the PassThruReceive Pipeline on the Receive Port

   2. Use the PassThruTransmit Pipeline on the Send Port

   3. Create a Map from the partner format to the Canonical invoice

   4. Create a Map from the Canonical invoice format to the desired partner format

   5. Apply a Map on the Send Port

3. HWLC Motors uses two BizTalk Servers, but only one Host (HostA) and one Host Instance per Server. High Availability is a requirement and this is the reason that two BizTalk Servers were set up. We want to ensure that FTP Receive only happens on one of the servers. What should you do (choose all that apply)?

   1. Turn off the Host Instance for HostA on one of the servers

   2. Create a new Host (HostB)

   3. Cluster HostB

   4. Create a Receive Handler for the FTP Adapter for HostB, and delete the Receive Handler for HostA

   5. Make all Receive Locations using the FTP Handler run under HostB

4. You have several Pipelines, both Receive and Send, deployed in a BizTalk Application Common. The Pipelines will be needed in several Applications. You create a new Application ApplicationA, and start to create Receive Ports and Receive Locations. When choosing a Pipeline for your Receive Location, you notice that the Pipelines deployed in the Common Application do not appear in the drop-down list of available Receive Pipelines. What should you do?

   1. Make a reference to the default BizTalk Application in ApplicationA

   2. Redeploy all the Pipelines in the ApplicationA Application

   3. Make a reference to the Common Application in ApplicationA

   4. Make a reference to ApplicationA in Common

5. You want to make sure that all Receive Locations in the entire BizTalk Group are disabled. What should you do?

   1. Stop all running Host Instances.

   2. In the BizTalk Administration Console, open the Group Hub and choose New Query. Query the Running Service Instances and make sure that the query doesn't return any rows.

   3. In the BizTalk Administration Console, open the Group Hub and select Applications. Check that all Applications are in a stopped state.

   4. In the BizTalk Administration Console, choose the All Artifacts Application and open Receive Locations. Check that all locations are disabled.

6. You are deploying a Receive Port in your production environment. You do not want it to automatically start processing messages until June 5, 2014. How do you enable this?

   1. In the Receive Port, enable the Service Window and set it to stop at 05:00 (5 am) and start at 20:14 (8:14 pm)

   2. In the Receive Port, configure the Schedule Stop date to June 5, 2014

   3. In the Receive Port, configure the Schedule Start date to June 5, 2014

   4. In the Receive Port, enable the Service Window and set it to start at 05:00 (5 am) and stop at 20:14 (8:14 pm)