PL-400 Practice Test

Answer choices

1. A. Hard-coded production URLs in every component, for the stated security, delivery, and accountability requirements.
2. B. Business records edited after import, for the stated build power platform solutions requirement.
3. C. A solution environment variable with a value supplied for each environment
4. D. A PCF global variable, under the described build power platform solutions criteria.

Wrong-answer review

• A. Hard-coded production URLs in every component, for the stated security, delivery, and accountability requirements.: Hard coding prevents safe promotion and exposes production details in lower environments.
• B. Business records edited after import, for the stated build power platform solutions requirement.: Ordinary data is not the supported portable configuration component for this purpose.
• D. A PCF global variable, under the described build power platform solutions criteria.: A control variable cannot configure unrelated apps and flows across environments.

Answer choices

1. A. An asynchronous Service Bus queue for competing order workers and a topic with three subscriptions for audit consumers, as the organization’s selected response.
2. B. One synchronous webhook that calls all four consumers serially, as the primary implementation for the described business requirement.
3. C. A queue with all audit consumers reading the same message competitively, as the recommended implementation across the complete governed service lifecycle.
4. D. A form OnSave handler that sends events from the browser, within the documented operational, security, ownership, and validation requirements.

Answer choices

1. A. Two canvas collections, for the described technical objective and its associated operational control requirements, for the stated create a technical design requirement.
2. B. A PCF control for both responsibilities, for the described technical objective and its associated operational control requirements, for consideration.
3. C. A custom connector for the REST API and a custom API for the Dataverse message
4. D. Two security roles, as the selected approach for the stated technical and business outcome, for this task.

Answer choices

1. A. Keep status only in Function memory and retry 429 immediately, for the described technical objective and its associated operational control requirements, as configured.
2. B. Move the work into synchronous PreOperation so users wait for completion, as the primary implementation for the described business requirement.
3. C. Persist processing status, make work idempotent, isolate poison messages, emit correlated telemetry, and honor Dataverse retry guidance, under the proposed approach.
4. D. Discard failed messages and mark every row Completed, within the documented operational, security, ownership, and validation requirements.

Answer choices

1. A. Employ the Virtual Agent Connector to automate responses based on Dataverse table data.
2. B. Utilize the CDS Connector to trigger a Power Automate flow within a specific business process.
3. C. Leverage the Logic Apps Connector to orchestrate a sequence of actions across multiple systems.
4. D. Run a table-bound Dataverse action, including supported custom actions

Answer choices

1. A. Keep Xrm.Page and poll the field with setInterval, within the defined security and accountability boundaries.
2. B. Move the validation into a PCF manifest description, under the stated technical, operational, and governance constraints.
3. C. Use executionContext to obtain formContext and register the handler on the field's OnChange event, within the described context.
4. D. Register the same function only for form OnLoad twice, as the recommended implementation across the complete governed service lifecycle.

Answer choices

1. A. Load all transaction rows into a collection during App.OnStart, as the proposed design for the complete governed operational workflow.
2. B. Use nondelegable filters so the device performs every search, for the described technical objective and its associated operational control requirements.
3. C. Use delegable filters and explicit column selection for transactions, while caching only the small reused status lookup
4. D. Add every table column to each gallery item, as the recommended implementation across the complete governed service lifecycle.

Answer choices

1. A. Move the testers into production where more records exist, for the described technical objective and its associated operational control requirements.
2. B. Make every tester System Administrator in all environments, for the described technical objective and its associated operational control requirements, for consideration.
3. C. Grant an appropriate privilege depth or team-based access to the required test Orders without adding broad unrelated privileges, within organization-wide risk-and-accountability boundaries.
4. D. Rebuild the app as a canvas app to avoid Dataverse security, under the stated technical, operational, and governance constraints.

Answer choices

1. A. Before applying the page, and generate a new Account Number on restart, for the described technical objective and its associated operational control requirements.
2. B. Use Account Number as an alternate key and persist the token only after the corresponding page is successfully applied
3. C. After receiving the page even if target writes fail, as the selected approach for the stated technical and business outcome.
4. D. Never store tokens; scan every Account on each run, for the described technical objective and its associated operational control requirements, in context.

Answer choices

1. A. Update the column label through supported Dataverse metadata customization
2. B. Rename the column's logical name and recreate all existing plug-in references
3. C. Change only the column's caption on one model-driven form
4. D. Update the column description while keeping its existing display label