DRAG DROP
###BeginCaseStudy###
Case Study: 1
Scenario 1
Background
You are developing a flight information consolidation service. The service retrieves flight
information from a number of sources and combines them into a single data set. The
consolidated flight information is stored in a SQL Server database. Customers can query
and retrieve the data by using a REST API provided by the service. The service also offers
access to historical flight information. The historical flight information can be filtered and
queried in an ad hoc manner. The service runs on a Windows Azure Web Role. SSL is not
used.
Business Requirements
• A new data source for historical flight information is being developed by a contractor
located on another continent.
• If a time zone is not specified, then it should be interpreted as Coordinated Universal
Time (UTC).
• When you upgrade a service from a staging deployment to a production deployment,
the time that the service is unavailable must be minimized.
• The default port must be used for HTTP.
Technical Requirements
The existing sources of flight information and the mechanism of exchange are listed below.
• Blue Yonder Airlines provides flight information in an XML file.
• Consolidated Messenger provides flight information in a Microsoft Access database
that is uploaded every 12 hours to the service using SFTP. The company uses port 22 for
SFTP.
• Margie’s Travel provides and consumes flight information using serialized ADO.NET
DataSets. Data is periodically synced between the service and Margie’s Travel.
• Trey Research provides data from multiple sources serialized in proprietary binary
formats. The data must be read by using .NET assemblies provided by Trey Research. The
assemblies use a common set of dependencies. The current version of the Trey Research
assemblies is 1.2.0.0. All assemblies provided by Trey Research are signed with a key pair
contained in a file named Trey.snk, which Trey Research also supplies.
• The application specification requires that any third-party assemblies must have
strong names.
Application Structure
###EndCaseStudy###
The service has been deployed to Windows Azure. Trey Research has provided version
1.3.0.0 of the assembly to support a change in the serialization format. The service must
remain available during the transition to the new serialization format. You need to ensure
that the service is using the new assembly. Which configuration setting should you add to
the web.config? (To answer, drag the appropriate configuration elements to the correct
location or locations in the answer area. Each configuration element may be used once,
more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Explanation:
See: http://msdn.microsoft.com/en-us/library/7wd6ex19.aspx
I think the correct answer is instead of
bindingRedirect instead of codebase
Correct answer should be
Culled from: Exam Ref 70-487:Developing Windows Azure and Web Services (Pg. 424)
binding redirect oldVersion=”1.2.0.0″ newVersion=”1.3.0.0″
Yes, this is the answer. The link in the explanation also states this.
yes the answer is
..
..
<binding redirect oldVersion=”1.2.0.0″ newVersion=”1.3.0.0″?
..
..
verified from Exam Ref 70-487:Developing Windows Azure and Web Services (Pg. 424)