nerdexam
Microsoft

PL-400 · Question #80

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…

The correct answer is B. No. B is correct because adding a JavaScript library to the Events tab only registers it for specific form events, and the Non-Event Dependencies tab is designed to declare which fields a script library accesses outside of those events - but this configuration alone does not…

Submitted by jakub_pl· Apr 18, 2026

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. A Common Data Service (CDS) environment has two custom entities named Building code and Work item. Building code has a code date custom field and Work item has an elapsed time custom field. Construction workers use a consolidated custom form with data from both entities to fill.in their daily work items. A JavaScript library is used with these custom entities and fields to apply complex logic. You need to ensure that the JavaScript library continues to function as originally designed if other developers expand the environment. Solution: In form properties of the consolidated form, add the JavaScript library in the events tab and add the two custom fields to the dependent fields section of the non-event dependencies tab. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(46 responses)
  • A
    28% (13)
  • B
    72% (33)

Explanation

B is correct because adding a JavaScript library to the Events tab only registers it for specific form events, and the Non-Event Dependencies tab is designed to declare which fields a script library accesses outside of those events - but this configuration alone does not guarantee the library continues to function when other developers expand the environment. The Non-Event Dependencies section tracks the form's primary entity fields; however, since this consolidated form pulls data from two separate entities (Building code and Work item), dependencies on fields from the secondary entity are not fully protected by this mechanism. To truly safeguard the library against breaking changes, the solution should also ensure the JavaScript web resource and its dependent fields are declared as solution-level component dependencies, which prevents other developers from inadvertently removing or modifying them.

Why A is wrong: Simply registering the library and declaring non-event field dependencies is a partial measure - it helps the form load required field data, but it does not enforce protection against schema changes made by other developers at the environment level.

Memory tip: Think of Non-Event Dependencies as a post-it note telling the form "load these fields too" - it's a hint, not a lock. To truly protect a library across a multi-developer environment, you need solution-level dependency tracking, which acts as the actual lock.

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PL-400 Practice