Home » Microsoft » 70-487 v.2 » 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?
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:
Correct Answer:
Explanation/Reference:
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
Target 1: wsHttpBinding
Target 2: timeout
Target 3: wsHttpBinding
Target 4: timeout
Target 5: closeTimeOut
Target 6: 03:00:00
Target 7: wsHttpBinding
It should be:
Target 1: basicHttpBinding (becasue it requires for old asp.net web services – only universal basicHttpBinding )
Target 2: closeTimeOut
Target 3: basicHttpBinding
Target 4: timeOut (it’s just value of the name!)
Target 5: closeTimeOut (no timeout attribute, only closeTimeOut)
Target 6: 03:00:00
Target 7: basicHttpBinding
sorry. Looks like it’s wsHttpBinding, because it uses security features and transaction control
Target 1: wsHttpBinding
Target 2: timeout (it’s just value of the name!)
Target 3: wsHttpBinding
Target 4: timeOut (it’s just value of the name!)
Target 5: closeTimeOut (no timeout attribute, only closeTimeOut)
Target 6: 03:00:00
Target 7: basicHttpBinding
basicHttpBinding works for this case.
basicHttpBinding has timeOut attribute.
@Edward It works, but they are specifically mentioning it must be interopable with ASP.NET web service clients. I feel like they are hinting towards the ws binding.
About the timeout property, are you referring to this article?:
https://docs.microsoft.com/en-us/dotnet/framework/wcf/configuring-bindings-for-wcf-services#specifying-a-service-with-two-endpoints-using-different-binding-values
I can’t find it elsewhere and it is not explained here. Do you maybe have another link to verify that?
there is no timeout attribute for any bindings. Only CloseTimeout, OpenTimeout, SendTimeout.
https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/configuring-timeout-values-on-a-binding
We can use basicHttpBinding. basicHttpBinding has timeout attribute.
https://docs.microsoft.com/en-us/dotnet/api/system.servicemodel.basichttpbinding?view=netframework-4.8
https://docs.microsoft.com/en-us/dotnet/framework/wcf/configuring-bindings-for-wcf-services
I think we can use basicHttpBinding
basicHttpBinding has timeOut attribute.
See attached references:
https://docs.microsoft.com/en-us/dotnet/api/system.servicemodel.basichttpbinding?view=netframework-4.8
https://docs.microsoft.com/en-us/dotnet/framework/wcf/configuring-bindings-for-wcf-services
“The service must be interoperable with ASP.NET web service clients”
wsHttpBinding (targets 1, 3, 7)
https://docs.microsoft.com/en-us/dotnet/framework/wcf/bindings-overview#system-provided-bindings
targets 2 and 4 need to be equal but can be anything. Maybe Microsoft wants us to pick “timeout” for this, since otherwise it is not a valid option
target 5: timeout is not a valid option, so it has to be closeTimeout.
Target 1: basicHttpBinding
Target 2: closeTimeOut
Target 3: basicHttpBinding
Target 4: closeTimeout
Target 5: timeOut
Target 6: 03:00:00
Target 7: basicHttpBinding