After deploying a new Avaya Aura Session Manager (SM), what is its initial Service State?

Question

Options

• AAccept New Service
• BDeny All Service
• CService Mode
• DMaintenance Mode

• A
  3% (2)
• B
  3% (2)
• C
  7% (4)
• D
  87% (52)

Explanation

When a newly deployed Avaya Aura Session Manager first comes online, it defaults to Maintenance Mode (D) - a deliberate safe state that prevents the system from handling production traffic until an administrator has completed configuration and verified the deployment is ready. This protects the network from routing calls through an unconfigured or unverified system.

Why the distractors are wrong:

• A (Accept New Service) is a state an administrator manually sets after confirming the SM is properly configured - it must be explicitly enabled, never automatic at deployment.
• B (Deny All Service) is also an administrator-applied state used to intentionally block traffic (e.g., during maintenance windows), not the boot-time default.
• C (Service Mode) is not a valid Avaya SM service state designation; it's a plausible-sounding distractor with no corresponding real state.

Memory tip: Think of Maintenance Mode as the "out of the box" state - like a new appliance that's powered on but not yet plugged into the network for live use. An admin must take deliberate action to promote the SM to active service.

No community discussion yet for this question.