Refer to the exhibit. A POST /discovery request spawns an asynchronous task. After querying for more information about the task, the Cisco Catalyst Center (formerly DNA Center) platform returns the RE

Question

Exhibits

Options

• Arestarted
• Bsuccessful
• Cfailed
• Dstopped

• A
  2% (1)
• B
  91% (40)
• C
  5% (2)
• D
  2% (1)

Explanation

Explanation

When Cisco Catalyst Center returns a REST API response for an asynchronous discovery task, the progress field (or endTime combined with isError: false) in the JSON response indicates the task completed without errors - this maps to a "successful" status, making Option B correct. In Catalyst Center's Task API responses, a task showing "isError": false along with a populated endTime and progress indicating completion confirms the task succeeded.

• Option A (restarted) is incorrect because "restarted" is not a standard task status returned in Catalyst Center's task API response fields.
• Option C (failed) would require "isError": true in the response, along with an error-related failure message in the progress or description fields.
• Option D (stopped) is incorrect because a stopped/terminated task would reflect a different state indicator, not the completion fields shown in a successful response.

Memory Tip: When reading Catalyst Center async task responses, focus on the isError field - think of it as a simple pass/fail flag: false = success , true = failure . If there's no error flag and an end time exists, the task finished successfully.

No community discussion yet for this question.