nerdexam
Cisco

300-920 · Question #41

Which two filters are valid for limiting a webhook? (Choose two.)

The correct answer is A. roomId=<roomId> B. personId!=<personId>. Option A (roomId=<roomId>) is a valid equality filter using the correct field name roomId and proper = operator. Option B (personId!=<personId>) is valid because Webex webhook filters support the != (not-equal) operator to exclude events involving a specific person - useful for…

Webex API Foundation

Question

Which two filters are valid for limiting a webhook? (Choose two.)

Options

  • AroomId=<roomId>
  • BpersonId!=<personId>
  • CspaceId=<spaceId>
  • DpersonId=<personId>$spaceId=<spaceId>
  • EpersonId=<personId>$roomId=<roomId>

How the community answered

(36 responses)
  • A
    92% (33)
  • C
    6% (2)
  • E
    3% (1)

Explanation

Option A (roomId=<roomId>) is a valid equality filter using the correct field name roomId and proper = operator. Option B (personId!=<personId>) is valid because Webex webhook filters support the != (not-equal) operator to exclude events involving a specific person - useful for filtering out bot-generated events.

Option C is wrong because the correct field name is roomId, not spaceId - even though Webex sometimes uses "space" informally, the API parameter is roomId. Options D and E are both invalid because they use $ to combine multiple filters; the correct delimiter for combining filter conditions is & (e.g., personId=<personId>&roomId=<roomId>). Option D also compounds the error by using the invalid spaceId field name.

Memory tip: Think "Right field, Right operator, Right separator" - roomId (not spaceId), != is allowed, and & joins filters (not $). If any of those three are wrong, the filter is invalid.

Topics

#Webhook filters#Event subscriptions#Filter operators

Community Discussion

No community discussion yet for this question.

Full 300-920 Practice