Which two states are applications expected to be seen in when they are managed on Cisco IOx? (Choose two.)

Question

Options

• ADEACTIVATED
• BACTIVATED
• CALLOWED
• DSTOPPED
• EVALIDATED

• B
  94% (33)
• C
  3% (1)
• E
  3% (1)

Explanation

Cisco IOx defines a specific application lifecycle with recognized states, and ACTIVATED and STOPPED are two of the valid states an application can occupy during management. ACTIVATED means the app has been installed and had resources allocated to it (CPU, memory, networking) but is not yet running, while STOPPED means the application was previously running and has since been halted - both are normal operational states visible through the IOx Local Manager or CLI.

Why the distractors are wrong:

• A. DEACTIVATED - not a valid IOx state label; when you deactivate an app, it returns to the DEPLOYED state, not "DEACTIVATED"
• C. ALLOWED - a policy/ACL concept, not an IOx application lifecycle state
• E. VALIDATED - not a defined IOx state; this may confuse candidates who associate validation with install/deploy checks

Memory tip: Think of the IOx app lifecycle as a pipeline - DEPLOY → ACTIVATE → START/STOP. The two "pause points" you'd commonly manage an app in are ACTIVATED (resources ready, not yet running) and STOPPED (was running, now paused) - both represent stable, managed states rather than transitional ones.

No community discussion yet for this question.