Question 1

What is the correct procedure for connecting to the Application Enablement Services (AES) command-line interface (CLI), and the default login ID?

Options :

A : Use PuTTY or equivalent to SSH to < AES IP address > using port 22, then enter login=cust.

B : Use PuTTY or equivalent to SSH to < AES IP address > using port 22, then enter login=craft.

C : Use PuTTY or equivalent to connect to < AES IP address > using port 21, then enter login=admin.

D : Use PuTTY or equivalent to SSH to < AES IP address > using port 222, then enter login = ipcs.

Answer: B

Question 2

What is the correct URL for connecting to the Application Enablement Services (AES) web interface, and the default login ID?

Options :

A : https://, then enter login=cust

B : https:///admin, then enter login=ucsec

C : https://:8443, then enter login=craft

D : http://, then enter login=admin

Answer: C

Question 3

When the Branch Session Manager (BSM) sends OPTIONS requests to the Survivable Communication Manager (CM) when the Main Communication Manager and the Core Session Managers are in a working condition and reachable, what would be the SIP response?

Options :

A : 503 Service Unavailable (LSP is inactive)

B : 503 Service Unavailable (No Media Resources)

C : 200 OK

D : 488 Not Acceptable Here

Answer: B

Question 4

What must be configured under DMZ Services in the Avaya Session Border Controller for Enterprise (ASBCE) to allow downloading the 46xxsettings.txt file to a Remote Worker device?

Options :

A : File Transfer

B : Mapping Profile

C : Reverse Proxy

D : Application Relay

Answer: C

Question 5

In some deployments, the Avaya Session Border Controller for Enterprise (ASBCE) might not trust the Certificate Authority (CA) which signed the WebLM server identity certificate. Which tool would you use to fix the trust issue?

Options :

A : the "Fix ASBCE WebLM Cert" option under Device Management > Licensing

B : the sbceconfigurator.py fix-weblm-cert command issued from the EMS CLI

C : the sbceconfigurator.py change-ssl-certs command issued from the SBC CLI

D : the "Verify Existing Certificate" option under Device Management > Licensing

Answer: B