You are preparing to enable EASG to provide Avaya Services local and remote access for performing support and system optimization. What are the two methods to enable EASG during the implementation?…

Question

Options

• ADuring the OVA deployment
• BUsing the CLI command EASGManage after deployment
• COpen a ticket to Avaya services and request to enable it
• DUsing SMGR web GUI, check the "Enable EASG" check box on the desired component in the
• EUsing the SDM after the deployment

• A
  87% (45)
• C
  2% (1)
• D
  8% (4)
• E
  4% (2)

Explanation

EASG (Avaya Services Gateway) can be enabled in exactly two ways during implementation: at the time of OVA deployment by configuring it through the deployment wizard prompts, or post-deployment via the EASGManage CLI command - giving implementers flexibility to enable it either upfront or after the fact.

Why the distractors are wrong:

• C is incorrect because EASG is self-administered by the implementer; Avaya does not enable it remotely via a ticket - that would be a circular dependency for a remote access tool.
• D is incorrect because the SMGR (System Manager) web GUI checkbox method is not a supported activation path for EASG itself; SMGR manages other components but is not the mechanism for enabling EASG.
• E is incorrect because the SDM (Secure Desktop Manager or Service Delivery Manager depending on context) is not the designated tool for enabling EASG.

Memory tip: Think "Before or After" - you enable EASG either before the system is live (during OVA deployment) or after using the EASGManage CLI. Any other method (ticket, GUI, SDM) is a distractor because EASG is a self-service, CLI/deployment-driven feature by design.

No community discussion yet for this question.