A company has two development instances, two test instances, two staging instances, and one production instance. The test team reports connection issues with the test and staging instances. You need…

Question

Options

• Ahttps://globaldisco.crm.dynamics.com/api/discovery/v9.1/instances
• Bhttps://myorg.api.crm.dynamics.com/api/data/v9.1/
• Chttps://dev.crm.dynamics.com/api/discovery/v9.1/instances
• Dhttps://disco.crm.dynamics.com/api/discovery/v9.1/
• Ehttps://dev.crm.dynamics.com/api/discovery/v9.1/instances(UniqueName='myorg')

• A
  14% (5)
• B
  8% (3)
• C
  76% (28)
• D
  3% (1)

Explanation

The Dynamics 365 Discovery Service API is used to determine which CRM instances a user has access to. Option C (https://dev.crm.dynamics.com/api/discovery/v9.1/instances) queries the regional Discovery Service and returns all instances the authenticated user can access - this allows the team to see which test and staging instances are available to them. Option E (https://dev.crm.dynamics.com/api/discovery/v9.1/instances(UniqueName='myorg')) retrieves details for a specific instance by its unique name, confirming access to that particular instance. Option A uses the Global Discovery Service (globaldisco) which is a different endpoint pattern. Option B is a direct OData API endpoint, not a discovery endpoint. Option D uses the older 'disco' subdomain format which is deprecated.

No community discussion yet for this question.