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 sourcesserialized in proprietary binary formats. The datamust 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
********************************************************
DRAG DROP
You need to configure the Windows Azure service definition to enable Consolidated Messenger to upload files.
What should you do? (To answer, drag the appropriate configuration items to the correct location or locations.
Each configuration item may be used once, more thanonce, or not at all. You may need to drag the split bar
between panes or scroll to view content.)
Explanation:
InputEndpoint, http, 80
InputEndpoint, tcp, 22
Why not upload using HTTPS?
In the requirements it says to use http
para que pueda ser https es necesario que salga por el puerto 443 bueno tambien ser cambiado.
otro es que para configurar nuestro inputendpoint es necesario agregar el atributo certficate para adjuntar nuestro certificado que sera el encargado de encriptar la informacion que sera enviada entre cliente y servidor
ademas en el requerimiento dice claramente que usan el port por defecto 80 y ademas usand el protocolo http
PD: tambien la respuesta escorrecta cuando dice inputendpoint para el puerto TCP.
por que este permite manejar extranet osea tiene que se compartida entre distintas compaƱias
por lo tanto va estar espuesta y fuera de mi centro de datos teniendo que pasar por windows azure
por mi balanceador de carga. que la peticion de la compaƱia para la subida de archivo
debe estar expuesta.
es por esa razon que no se manejo internalendpoint:
por que este solamente funcionaria dentro de mi propio centro de datos al no ser expuesto
en internet ni pasar por mi balanceador de carga