exam questions

Exam 70-487 All Questions

View all questions & answers for the 70-487 exam

Exam 70-487 topic 1 question 30 discussion

Actual exam question from Microsoft's 70-487
Question #: 30
Topic #: 1
[All 70-487 Questions]

HOTSPOT -
You are developing a WCF service.
The service must be interoperable with ASP.NET web service clients. In addition, it must be a time-out of three hours.
You need to configure the service to meet the requirements.
You have the following markup:

Which markup segments should you include in Target 1, Target 2, Target 3, Target 4, Target 5, Target 6 and Target 7 to complete the markup? (To answer, select the appropriate markup segment from each drop-down list in the answer area.)
Hot Area:

Show Suggested Answer Hide Answer
Suggested Answer:
Target 1: wsHTTPBinding -
wsHttpBinding is the full-blown binding, which supports a ton of WS-* features and standards. It has lots more security features: you can use sessionful connections, you can use reliable messaging, you can use transactional control.
Incorrect: Not basicHttpBinding: basicHttpBinding is the very basic binding (SOAP 1.1). It is not much in terms of security, not much else in terms of features, but compatible to just about any SOAP client out there. It is great for interoperability, but weak on features and security.

Target 2: timeout -
Bindingconfiguration (Target 2) and Binding name (Target 4) must be the same. Timeout is not use elsewhere and is an appropriate choice.

Target 3: WSHttpBinding -

Target 4: timeout -
Bindingconfiguration (Target 2) and Binding name (Target 4) must be the same. Timeout is not use elsewhere and is an appropriate choice.

Target 5: CloseTimeout -
The following timeouts are available on WCF bindings: OpenTimeout, CloseTimeout, SendTimeout, and ReceiveTimeout.

Target 6: 03:00:00 -
3 hours, 0 minutes, and 0 seconds.

Target 7: WSHttpBinding -
Reference:
https://msdn.microsoft.com/en-us/library/hh924831(v=vs.110).aspx

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
MaverickCalibre
Highly Voted 5 years, 4 months ago
<configuration> <system.serviceModel> <services> <service name=”Mynamespace.Orderservice”> <endpoint address=”http://localhost” binding=”basicHttpBinding” contract=”Mynamespace.IOrderservice” bindingConfiguration=”timeout”> </endpoint> </service> </services> <bindings> <basicHttpBinding> <binding name=”timeout” closeTimeout=”03:00:00″ /> </basicHttpBinding> </bindings> </system.serviceModel> </configuration>
upvoted 16 times
MaverickCalibre
5 years, 4 months ago
https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/config-wcf-service-with-aspnet-web-service
upvoted 9 times
tanujgyan
4 years, 10 months ago
Thats correct
upvoted 1 times
...
applepie
4 years, 8 months ago
"To configure a Windows Communication Foundation (WCF) service endpoint to be interoperable with ASP.NET Web service clients, use the System.ServiceModel.BasicHttpBinding type as the binding type for your service endpoint." as the article above mentioned.
upvoted 3 times
...
...
Dreamchaser1980
4 years, 8 months ago
References: https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/wcf/basichttpbinding basicHttpBinding is the very basic binding - SOAP 1.1, not much in terms of security, not much else in terms of features - but compatible to just about any SOAP client out there https://stackoverflow.com/questions/2650785/basichttpbinding-vs-wshttpbinding-vs-webhttpbinding
upvoted 1 times
...
...
abalone
Highly Voted 5 years, 5 months ago
target 7: wsHttpBinding
upvoted 6 times
...
Ptu12125
Most Recent 4 years, 3 months ago
"To configure a Windows Communication Foundation (WCF) service endpoint to be interoperable with ASP.NET Web service clients, use the System.ServiceModel.BasicHttpBinding type as the binding type for your service endpoint." Ref:https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/config-wcf-service-with-aspnet-web-service
upvoted 1 times
...
kvijen
4 years, 5 months ago
basicHttpBinding timeout basicHttpBinding timeout closeTimeout 03:00:00 basicHttpBinding
upvoted 3 times
...
mr_
4 years, 9 months ago
I think that the most important here is: 'ASP.NET web service clients' -> which I understand as old ASMX (SOAP 1.1) web services. Because of that I would go for basicHttpBinding (SOAP 1.1) and not wsHttpBinding (SOAP 1.2). I may be wrong - that is just my impression. By the way - the name attribute is weird to be guessed - you can basically put everything there if I am not wrong...
upvoted 2 times
mr_
4 years, 9 months ago
I meant pair of attributes - 'bindingConfiguration' & 'name'.
upvoted 1 times
...
...
Victor_Yin
5 years ago
The answer is correct
upvoted 2 times
...
mmk1991
5 years, 1 month ago
<system.serviceModel> <services> <service name="MyNamespace.OrderService"> <endpoint address="" contract="" binding="basicHttpBinding" bindingConfiguration="basicHttpBinding"> </endpoint> </service> </services> <bindings> <basicHttpBinding> <binding name="basicHttpBinding" closeTimeout="03:00:00"> </binding> </basicHttpBinding> </bindings> </system.serviceModel>
upvoted 2 times
...
TinaZh
5 years, 3 months ago
Should be basicHttpBinding. "ASP.Net Web Service clients do not support WS-Security, so the BasicHttpBinding.Security should be set to Transport."
upvoted 4 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago