Avaya 71301X Online Practice Questions and Exam Preparation

Avaya 71301X Online Questions & Answers

• Question 21:

  Which two configuration steps must be performed on the Avaya Aura Communication Manager (CM) for integrating it with the Application Enablement Services (AES), and enabling the TSAPI link? (Choose two.)

  A. Create a CTI user.
  B. Configure IP Services.
  C. Create a Signaling Group.
  D. Create a CTI link.
  E. Configure Switch Connection.
  B. Configure IP Services.
  D. Create a CTI link.

  ---

  Explanation/Reference:

  To integrate Avaya Aura Communication Manager (CM) with Application Enablement Services (AES), and enable the TSAPI link, you need to perform two configuration steps on CM: Configure IP Services and Create a CTI link. These steps

  are necessary to establish a connection between CM and AES using ASAI protocol, which is a proprietary protocol that provides access to various CTI features of CM. A TSAPI link is a logical connection between CM and AES that allows

  TSAPI applications to use ASAI features through AES. To configure IP Services and Create a CTI link on CM, you need to use these screens:

  The "ip-services" screen: This is a screen that allows you to create and manage IP services on CM, such as ASAI-IP or C-LAN. You can access this screen using the System Access Terminal (SAT) interface of CM. On this screen, you need

  to specify a service type, node name, local node, local port, remote node, remote port, remote domain name, service state, and service link for each IP service. For integrating with AES, you need to create an ASAI-IP service that points to the

  node name of an AES server.

  The "cti-link" screen: This is a screen that allows you to create and manage CTI links on CM, which are logical connections between CM and CTI servers, such as AES. You can access this screen using the System Access Terminal (SAT)

  interface of CM. On this screen, you need to specify a name, number, type, and password for each CTI link. For integrating with AES, you need to create a CTI link of type ADJ-IP that matches the switch CTI link number on AES.

• Question 22:

  You are obtaining identity certificates and encryption keys from a Certificate Authority (CA) for installation on the Avaya Session Border Controller for Enterprise (ASBCE).

  Which statement about installing the identity certificate and encryption key files on the ASBCE is true?

  A. The filenames of the identity certificate (.pern or .crt file) and the encryption key (.key file) must match.
  B. Both the identity certificate and the encryption key files must be provided in a .zip archive for the installation on the ASBCE.
  C. It must be rebooted before the identity certificate and the encryption key installation.
  D. The filename of the identity certificate (.pern or .crt file) must be different from the filename of the encryption key (.key file).
  D. The filename of the identity certificate (.pern or .crt file) must be different from the filename of the encryption key (.key file).

  ---

  Explanation/Reference:

  When installing the identity certificate and encryption key files on the Avaya Session Border Controller for Enterprise (ASBCE), you need to follow this rule: The filename of the identity certificate (.pem or .crt file) must be different from the filename of the encryption key (.key file). An identity certificate is a file that contains information about the identity and public key of an entity, such as a server or an endpoint. An encryption key is a file that contains information about the private key of an entity, which is used to encrypt and decrypt data. The identity certificate and encryption key files are obtained from a Certificate Authority (CA) or generated by yourself using tools such as OpenSSL. When installing these files on the ASBCE server, you need to make sure that they have different filenames, otherwise they will overwriteeach other and cause errors. For example, you can name them as sbce-cert.pem and sbce-key.key respectively.

• Question 23:

  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?

  A. File Transfer
  B. Mapping Profile
  C. Reverse Proxy
  D. Application Relay
  C. Reverse Proxy

  ---

  Explanation/Reference:

  To allow downloading the 46xxsettings.txt file to a Remote Worker device, you need to configure a Reverse Proxy under DMZ Services in the Avaya Session Border Controller for Enterprise (ASBCE). A Reverse Proxy is a configuration object that enables secure access to internal web servers from external clients. The Reverse Proxy intercepts HTTP or HTTPS requests from external clients and forwards them to the appropriate internal web servers, such as an HTTP server or an Avaya Aura Device Services (AADS) server. The Reverse Proxy also returns the responses from the internal web servers to the external clients. The 46xxsettings.txt file is a configuration file that contains settings for Avaya IP Deskphones, such as firmware versions, network parameters, and feature options. The 46xxsettings.txt file is usually hosted on an HTTP server or an AADS server in the enterprise network. To allow Remote Worker devices to download this file securely, you need to configure a Reverse Proxy that maps the external URL of the file to the internal URL of the file on the HTTP server or AADS server

• Question 24:

  When registering as a Remote Worker via the Avaya Session Border Controller for Enterprise (ASBCE), which IP address should be configured in the Server List of the Avaya one-X?Communicator?

  A. Avaya Aura Session Manager (SM) External (Public) Interface IP address allocated for Remote Workers
  B. The Avaya Aura^ Session Manager (SM) Security Module IP Address
  C. ASBCE External (Public) Interface IP address allocated for Remote Workers
  D. ASBCE Internal (Private) Interface IP address allocated for Remote Workers
  C. ASBCE External (Public) Interface IP address allocated for Remote Workers

  ---

  Explanation/Reference:

  When registering as a Remote Worker via the Avaya Session Border Controller for Enterprise (ASBCE), you should configure the ASBCE External (Public) Interface IP address allocated for Remote Workers in the Server List of the Avaya one-X?Communicator. The ASBCE External (Public) Interface is the interface that connects the ASBCE server to the public Internet and allows communication with external entities, such as Remote Workers or SIP service providers. The ASBCE server acts as a proxy for the Remote Workers and handles the SIP registration and call signaling with the Avaya Aura Session Manager (SM). Therefore, you need to specify the ASBCE External (Public) Interface IP address as the SIP server address in the Avaya one-X?Communicator settings

• Question 25:

  Which statement about SIP Entities being required to support Avaya Aura Presence Services hosted on a single Avaya Breeze?server is true?

  A. Only one SIP Entity is required, using the Avaya Breeze?server Security Module IP address. This SIP Entity should have the type Presence Services selected.
  B. Only one SIP Entity is required, using the Avaya Breeze?server Security Module IP address. This SIP Entity should have the type Avaya Breeze?selected.
  C. Two SIP Entities are required, using the same Avaya Breeze?server Security Module IP address. One SIP Entity should have the type Avaya Breeze?selected, and the other should have the type Other selected.
  D. Two SIP Entities are required, using the same Avaya Breeze?server Security Module IP address. One SIP Entity should have the type Avaya Breeze?selected, and the other should have the type Presence Services selected.
  D. Two SIP Entities are required, using the same Avaya Breeze?server Security Module IP address. One SIP Entity should have the type Avaya Breeze?selected, and the other should have the type Presence Services selected.

  ---

  Explanation/Reference:

  When deploying Avaya Aura Presence Services as a snap-in on a single Avaya Breeze?server, you need to create two SIP Entities for the same Avaya Breeze?server Security Module IP address or FQDN in System Manager. One SIP Entity is used for the Avaya Breeze?platform itself, and the other SIP Entity is used for the Presence Services snap-in. The type of the SIP Entity determines how Session Manager routes SIP messages to the Avaya Breeze?server. The type Avaya Breeze?indicates that the SIP Entity is a generic Avaya Breeze?server that canhost any snap-in. The type Presence Services indicates that the SIP Entity is a specific Avaya Breeze?server that hosts the Presence Services snap-in12

• Question 26:

  You need to connect the Avaya Breeze?platform that is hosting an Avaya Aura Presence Services snap-in with the Avaya Aura Session Manager (SM). Which three are required to set up this connection? (Choose three.)

  A. One Entity Link from SM to Avaya Breeze?
  B. one Entity Link from SM to Avaya Aura Presence Services Snap-in
  C. TLS ports 5061 and TLS 5062
  D. UDP port 5060 and TLS port 5061
  E. TCP port 5060 and UDP port 5060
  A. One Entity Link from SM to Avaya Breeze?
  C. TLS ports 5061 and TLS 5062
  D. UDP port 5060 and TLS port 5061

  ---

  Explanation/Reference:

  To connect the Avaya Breeze?platform that is hosting an Avaya Aura Presence Services snap-in with the Avaya Aura Session Manager (SM), you need to configure the following: One Entity Link from SM to Avaya Breeze? This is a SIP trunk that connects the SM and the Avaya Breeze?server for SIP signaling and media. You need to create an Entity Link in System Manager, under Elements > Routing > Entity Links, and specify the IP address or FQDN of the SM and the Avaya Breeze?server Security Module (SM100). You also need to select TLS as the SIP Link Transport Type56 TLS ports 5061 and TLS 5062: These are the ports used by the Entity Link for secure SIP signaling between SM and Avaya Breeze? Port 5061 is used by SM to send SIP requests to Avaya Breeze? while port 5062 is used by Avaya Breeze? to send SIP responses to SM. These ports require a valid certificate on both SM and Avaya Breeze?servers56 UDP port 5060 and TLS port 5061: These are the ports used by the Presence Services snap-in for XMPP federation with other XMPP servers or clients. Port 5060 is used for unencrypted XMPP traffic over UDP, while port 5061 is used for encrypted XMPP traffic over TLS. These ports enable presence and instant messaging features across different domains or platforms34

• Question 27:

  In the Avaya Session Border Controller for Enterprise (ASBCE), what is the state of a Network Interface, after the deployment?

  A. Deployed
  B. Active
  C. Disabled
  D. Enabled
  C. Disabled

  ---

  Explanation/Reference:

  In the Avaya Session Border Controller for Enterprise (ASBCE), the state of a Network Interface, after the deployment, is Disabled. A Network Interface is a logical interface that represents a physical port on the ASBCE server. A Network Interface can be configured with an IP address, subnet mask, gateway, and VLAN ID. After the deployment of the ASBCE server, the Network Interfaces are in a Disabled state by default. To enable a Network Interface, you need to use the ASBCE web interface or CLI and configure the interface parameters. You also need to assign the interface to a Zone, which is a logical grouping of interfaces that defines the security and routing policies for the ASBCE server

• Question 28:

  In the Avaya Session Border Controller for Enterprise (ASBCB) Multi-Server/ HA deployments, where do you access the tracesbc tool that displays SIP messages in real- time as they pass through the ASBCE?

  A. from the EMS component / device command line via SSH session using PuTTY
  B. from the SBC component/ device command line via SSH session using PuTTY
  C. from the Avaya Aura System Manager (SMGR) web interface, under the Elements>; Session Border Controller for Enterprise > Session Border Controller menu
  D. from the EMS web interface
  B. from the SBC component/ device command line via SSH session using PuTTY

  ---

  Explanation/Reference:

  In the Avaya Session Border Controller for Enterprise (ASBCB) Multi-Server/ HA deployments, you can access the tracesbc tool that displays SIP messages in real-time as they pass through the ASBCE from the SBC component/ device command line via SSH session using PuTTY. A Multi-Server/ HA deployment is a deployment where two or more ASBCE servers are deployed in a pair or cluster, providing redundancy and scalability for the ASBCE server. Each ASBCE server consists of two components: the EMS component and the SBC component. The EMS component is responsible for managing and monitoring the ASBCE server, while the SBC component is responsible for processing and routing the SIP traffic. The tracesbc tool is a CLI tool that runs on the SBC component and captures and displays SIP messages and mediastatistics for calls that traverse the ASBCE server. You can use PuTTY, which is a terminal emulator application, to establish an SSH session with the SBC component and run the tracesbc tool from the command line.

• Question 29:

  Which statement regarding the Survivable Communication Manager (CM) is true?

  A. It is configured on the System Manager (SMGR) as a SIP Entity, with an Entity Unk to the BSM.
  B. It is configured on the System Manager (SMGR) as a SIP Entity, with Entity Links to the Core Session Managers.
  C. It is configured on the System Manager (SMGR) as a Managed Element.
  D. It does not require configuring on the System Manager (SMGR) either as a Managed Element, or as a SIP Entity.
  C. It is configured on the System Manager (SMGR) as a Managed Element.

  ---

  Explanation/Reference:

  The Survivable Communication Manager (CM) is configured on the System Manager (SMGR) as a Managed Element. A Managed Element is an entity that can be managed by SMGR, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform. A Survivable CM is a Communication Manager instance that provides local call processing and trunking capabilities for remote sites or branches in case of a WAN outage or loss of connectivity with the core servers. A Survivable CM can be deployed on an S8300D server or on an external server such as Dell R620/R630 or HP DL360 G8/G9. To configure a Survivable CM as a Managed Element on SMGR, you need to specify its name, type, IP address, login credentials, and security settings56

• Question 30:

  Refer to the exhibit.

  

  Before you can begin configuring SIP Trunking, which status should all the Avaya Session Border Controller for Enterprise (ASBCE) components / devices show on the Device Management screen?

  A. Registered
  B. Provisioned
  C. Commissioned
  D. Ready
  D. Ready

  ---

  Explanation/Reference:

  Before you can begin configuring SIP Trunking, the status that all the Avaya Session Border Controller for Enterprise (ASBCE) components / devices should show on the Device Management screen is Ready. The Device Management screen is a web interface that allows you to view and manage the ASBCE components / devices, such as EMS (Element Management System), SBC (Session Border Controller), or HCA (High Capacity Appliance). The Device Management screen displays information such as device name, management IP, version, status, reboot, and shutdown for each component / device. The status indicates the operational state of the component / device, which can be one of these values: Provisioned, Commissioned, Registered, or Ready. The Ready status means that the component / device is fully operational and ready to handle traffic. Therefore, before configuring SIP Trunking, you should make sure that all the ASBCE components / devices have a Ready status on the Device Management screen.