300-920 Question #6: Real Exam Question with Answer & Explanation

The correct answer is B. Set x.Type to `pressed' instead of `released'.. Option B is correct because Cisco xAPI split button widgets emit two sequential events - pressed (when the button is activated with its selected value) and released (when the physical press ends, which may carry no meaningful widget value). When the code listens for released, the

Webex Devices and SDKs

Question

Refer to the exhibit. Certain lighting conditions are needed when hosting Webex meetings for a particular department in a company. A split button that integrates with the lighting controls is added to the Touch 10. However, when the user selects Chill, the lights turn off completely. Which code change resolves this issue?

Exhibit

Options

AChange xapi.event to xapi.httpfeedback.
BSet x.Type to pressed' instead of released'.
CSet x.Type to clicked' instead of released'.
DPass x.Value instead of x to the lights function.

Explanation

Option B is correct because Cisco xAPI split button widgets emit two sequential events - pressed (when the button is activated with its selected value) and released (when the physical press ends, which may carry no meaningful widget value). When the code listens for released, the lights function receives an empty or null value, which the lighting system interprets as "off," regardless of which option the user selected.

Why the others are wrong:

A - xapi.httpfeedback is an unrelated mechanism for registering HTTP callbacks; the bug is in which event phase is handled, not the feedback channel used.
C - clicked is not a valid xAPI widget event type for Touch 10; only pressed and released exist, so this would break event detection entirely.
D - Passing x.Value instead of x changes what the lights function receives, not when the event fires; the real problem is that released delivers no valid selection state, so fixing the argument without fixing the event type still yields the wrong value.

Memory tip: Think "Press to Select" - for Cisco xAPI split buttons, the selection value lives on the pressed event. Released is the finger coming off the button, after the value is gone.

Topics

#Touch 10 button events#xAPI event handling#Device integration#Event type selection

Community Discussion

No community discussion yet for this question.

Full 300-920 Practice