You create a service and deploy it on a network in a building named Building1. You will deploy the service to Building2.
The service in Building1 is configured using the following discovery scopes.
<scopes>
<add scope=”http://contoso.com/Chicago/Building1″/>
<add scope=”ldap:///ou=Building1,ou=Chicago,o=contoso,c=us”/>
</scopes>
The service in Building2 will be configured using the following discovery scopes.
<scopes>
<add scope=”http://contoso.com/Chicago/Building2″/>
<add scope=”ldap:///ou=Building2,ou=Chicago,o=contoso,c=us”/>
</scopes>
You need to ensure that the client application can discover the service in Building1 or the service in Building2.
Which scopes should you add to the client configuration file?
A.
<scopes>
<add scope=”http://contoso.com/Chicago/*”/>
</scopes>
B.
<scopes>
<add scope=”http://contoso.com/Chicago”/>
</scopes>
C.
<scopes>
<add scope=”ldap:///ou=Building,ou=Chicago,o=contoso,c=us”/>
</scopes>
D.
<scopes>
<add scope=”ldap:///ou=*,o=contoso,c=us”/>
</scopes>
Explanation:
Configuring Discovery in a Configuration File
(http://msdn.microsoft.com/en-us/library/dd456792.aspx)
B