You develop a model-driven app in which client-side scripts are used extensively. Users report that forms load quickly but become unresponsive. You need to investigate the form issues before optimizin

The correct answer is B. Add the URL parameter &ribbondebug=true.. Adding ?ribbondebug=true (or &ribbondebug=true) to a model-driven app URL activates the ribbon/command bar debugger, which exposes performance timing data for all ribbon rules and JavaScript commands that execute on form load and interaction. Since the symptom is forms becoming u

Submitted by yuki_2020· Apr 18, 2026

Question

You develop a model-driven app in which client-side scripts are used extensively. Users report that forms load quickly but become unresponsive. You need to investigate the form issues before optimizing the forms. What should you do first?

Options

AUse a Quick View form.
BAdd the URL parameter &ribbondebug=true.
CRemove unused forms from the app.
DEnable Offline mode.
EDisable form event handlers.

How the community answered

(32 responses)

A
3% (1)
B
75% (24)
C
6% (2)
D
13% (4)
E
3% (1)

Explanation

Adding ?ribbondebug=true (or &ribbondebug=true) to a model-driven app URL activates the ribbon/command bar debugger, which exposes performance timing data for all ribbon rules and JavaScript commands that execute on form load and interaction. Since the symptom is forms becoming unresponsive after loading-consistent with heavy command bar script evaluation-this tool surfaces the bottleneck before any code changes are made. It is the investigation step, not an optimization. Disabling event handlers (E) would alter behavior rather than diagnose it. Removing unused forms (C) and using Quick View forms (A) are optimization steps, not diagnostic ones. Offline mode (D) is unrelated to script performance investigation.

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice