Module Assessment

1.

A developer builds a screen in a code app that lists only the available devices from a Dataverse device table, showing just the device name, status, and location columns. Which getAll option should the developer use to avoid retrieving unnecessary columns?

The orderBy option, set to sort by device name

The maxPageSize option, set to a small page size

The select option, limited to the three columns the screen renders

2.

A developer updates an allowance record after a manager approves a request, but the update payload includes every field retrieved earlier instead of only the approved amount. What risk does this create?

The update can unintentionally trigger business logic tied to fields that didn't actually change and can distort audit history

Dataverse rejects the update because it contains more than one changed field

The generated service automatically removes any fields that didn't change before sending the request

3.

A developer calls a Dataverse custom API that's bound to a table, so the action runs against one specific record of that table. What must the developer's code supply as the first argument to the generated service call?

The name of the Dataverse environment where the custom API is registered

The ID of the record the action operates on

The schema name of the custom API itself

4.

An organization wants an equipment-eligibility rule to produce the same result no matter whether a request comes from a code app, another application, or an automated process. Which approach best achieves this consistency?

Implement the eligibility rule separately in the client-side code of each calling application

Store the eligibility rule as a plain Dataverse table that each application queries and interprets independently

Package the eligibility rule as a Dataverse custom API that every caller invokes

5.

A Power Apps code app needs to read the fulfillment contact for approved equipment requests, a value stored as a Power Platform solution environment variable with the schema name eqp_FulfillmentContact. Which approach correctly reads that value at run time?

Add the native Dataverse request table as a data source using --table "@envvar:eqp_FulfillmentContact"

Call the generated RetrieveEnvironmentVariableValue function with DefinitionSchemaName set to eqp_FulfillmentContact

Set PA_CLI_ENVIRONMENT_ID on the machine that runs the deployment pipeline

Feedback