Your network contains a server named Server1 that has the Streaming Media Services server role installed.
Server1 has the WMS Http Server Control Protocol plug-in and the WMS Server RTSP Control Protocol plug-in enabled.
All client computers run Windows 7.
The corporate website contains links to on-demand media content that is hosted on Server1.
You install the Web Server (IIS) server role on Server1 by using the default settings.
You change the port of the WMS HTTP Server Control Protocol plug-in to 1450.
Users report that the links on the corporate website no longer work.
You need to ensure that the users can access the on-demand media content by clicking the links on the corporate website.
What should you do? (Each correct answer presents a complete solution. Choose three.)
A.
On Server1, bind the HTTP protocol of the Default Web Site to port 1450.
B.
On Server1, disable the Default Web Site
C.
On the corporate website, change the URLs of the links to use rtsp://server1.
D.
On the corporate website, change the URLs of the links to use mms://server1.
E.
On Server1, disable the WMS Server RTSP Control Protocol plug-in.
F.
On the corporate website, change the URLs of the links to use http://server1:1450.
Pretty buggy question imho.
Setting the iis default website to 1450 would conflict with wms http.
Of course turning of the default website nulls that.
Why install IIS at all in fact?
Regarding the choice of protocol since protocol rollover will eventually result in http 1450 at worst why not just start there, we only have to support windows 7 though so I guess rtsp is suitable but it would work with http…1450 too!
Terrible question. If anyone can clarify definitively the answer that would fantastic. I’ll bet no one can though. to my mind just setting the links to http…1450 would sort it, one step.
In the real world one tests and plans changes carefully… am losing faith in ms exams.
Right, in the real world we sometimes miss things, that’s why we test change carefully 😉
It says Each answer represents a *complete solution* not part of a solution a I originally thought.
therefore
CDF is the correct answer.
Implicit is that installing IIS broke the original links of http://server1 and now iis is responding on that port..
http://technet.microsoft.com/en-us/library/cc754336.aspx
Am happy to stand corrected if anyone else has a view to share..