Correct Answers: A, C and F
The Dataverse provides the web services as extension tools for interacting with the data and metadata. The Dataverse web services include Web API and Organization service. If you prefer to write the .Net code, the Organization service approach is the best bet. The Web API provides almost the same functionality by using the REST API protocol. The Organization service implements two assemblies: SDK assembly and XRM Tooling assembly for the Windows clients.
The API service limits protect the Dataverse service performance and availability. If some users send an extraordinary amount of requests that can affect the other users` operations, the Dataverse limits such a demand for its services.
The Dataverse service protection API limits are enforced per web server and user. They are based on three measures: Number of requests — the number of requests sent by a user. The limit is 6000 requests within the 5-minute sliding window.
Execution time — the combined time for all requests sent by a user. The limit is 20 minutes within the 5-minute sliding window.
Number of concurrent requests — the number of concurrent requests made by a user. The limit is 52 requests.
The Dataverse applies all these measures in combination. If a user crosses the API limit, the service sends an error.
In the Web API case, the API response will include an HTTP error 429 — Too many requests with a Retry-After header that provides the date and number of delay seconds.
For the Organization service, the response will include the TimeSpan value in the OrganizationServiceFault error details.
All other options are incorrect.
For more information about the Dataverse service protection API limits, please visit the below URLs:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/api-limits#how-service-protection-api-limits-are-enforced
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/api-limits