###BeginCaseStudy###
Testlet 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###
DRAG DROP
Historical flight information data will be stored in Windows Azure Table Storage using the FlightInfo class as the
table entity.
There are millions of entries in the table. Queries for historical flight information specify a set of airlines to
search and whether the query should return only late flights. Results should be ordered by flight name.
You need to specify which properties of the FlightInfo class should be used at the partition and row keys to
ensure that query results are returned as quickly as possible.
What should you do? (To answer, drag the appropriate properties to the correct location or locations in the
answer area. Each property 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.)
Select and Place:
Answer: 
There should be Flight + WasLate, is that correct?
That will provide information as quick as possible and can return ordered result.
Explain if I’m wrong.
0
1
its Airline and Flight.
Think of it as a dictionary, getting the airline as the key and flight as the value.
1
0
ok, but in question states that query should return only late flights, so maybe Airline + WasLate?
0
0
WasLate + Flight
0
0
Partition should be by something meaningfull like lastname. In this case it’s rather silly to have main value as WasLate {boolean true/false}. My guesses are: Airline + WasLate or Flight + WasLate.
0
0
+1
0
0
+1 to stenly
If you start thinking about partitions more like “groups”, there is only one solution.
see: https://docs.microsoft.com/en-us/azure/cosmos-db/table-storage-design-guide#how-your-choice-of-partitionkey-and-rowkey-impacts-query-performance
In this article is parition-key used to “group” differrent departments, so the note about dictionary is not correct.
Next, if you check https://dzone.com/articles/partitionkey-and-rowkey
there is explained the performance and it sais that the worse is searching on other properties than on keys.
So based on those facts it shoul be WasLate (PK) and Flight (RK). You’ll filter per the PK and imediatelly get all late flights, right?
If somebody doesnt agree, please explain why.
1
0
Department is a group here that hold many employees together, a partition is ok for a department, here different Airline with flight information, Airline is ok for partition
0
0
Since only late flight should be filtered on wat i considered here is to use the waslate for quick retrieval, why I disagree with flight is because there is nothing to uniquely distinguish it, so waslate is cool
0
0