Configuring a messaging architecture

1. Answer: d

   If multiple Ports need to implement the same subscription, Send Port Groups should be used so that the subscription only needs to be implemented once and any changes to the subscription can be maintained in one place.

2. Answers: b, d, e

   PassThruReceive on the receive side will cause BizTalk to not recognize the MessageType and therefore, we will not be able to Map on the Send Port. The Map should be from the canonical format to the partner format.

3. Answers: b, c, d, e

   We need a new Host so that HostA will still do all the work except receiving FTP. The new Host needs to be clustered so that if one server fails, a Host Instance will start on the other Server.

4. Answer: c

   This should be done using references and it is in the Application, which needs to access artifacts from another Application, the reference needs to be made. The same Pipelines cannot be redeployed in another Application in BizTalk when already residing in another Application.

5. Answer: d

   By choosing All artifacts, we can get an overview of everything inside BizTalk, not limited to a certain Application. The other answers either stops too much or otherwise doesn't fulfill the requirement of disabling all the locations.

6. Answer: c

   You should use the Schedule Start Date to allow the Port to start at a later date. Setting the stop date does not allow you to control the start date. Setting the service window controls what time of the day the Port runs but says nothing about which day it should start.