The client has finished deploying Avaya Aura® Communication Manager (CM) and has signed a service contract with Avaya for technical support. What should be done by the system administrator in CM to…

Question

Options

• AIt is not necessary to do something. Avaya Services can access by default
• BEASGManage -disableEASG
• CEASGManage -enableEASG
• DEASGTurnOn
• EEASGManage -turnonEASG

• B
  6% (1)
• C
  89% (16)
• E
  6% (1)

Explanation

Option C is correct because Avaya's Enhanced Access Security Gateway (EASG) is disabled by default after a fresh CM deployment. To allow Avaya Services remote login access for support, the administrator must explicitly run EASGManage -enableEASG on the CM server.

Why the distractors are wrong:

• A is incorrect because EASG is not enabled by default - Avaya designed it this way intentionally for security, requiring a deliberate administrative action.
• B (-disableEASG) does the exact opposite - it would revoke Avaya Services access, not grant it.
• D (EASGTurnOn) is not a valid EASG command; it uses incorrect syntax and does not exist in CM.
• E (-turnonEASG) is also invalid syntax - the correct flag is -enableEASG, not -turnonEASG.

Memory tip: Think of EASG as a security gate that ships locked. The admin holds the key - you must actively unlock it (-enableEASG) before Avaya support can walk through. If you see "turn on" or a missing hyphen/flag, it's a distractor using plausible-sounding but fabricated syntax.

No community discussion yet for this question.