nerdexam
Avaya

72201T · Question #107

A customer called Avaya Support after their telecom administrator was unable to add 50 new telephones for new hires. Avaya support determined that the number of telephones exceeded the capacity the…

The correct answer is D. Providing accurate licensing specification. Option D is correct because the root cause of the problem was that the system had a capacity limit the customer unknowingly exceeded - this is a licensing issue. Avaya systems require licenses that specify the maximum number of endpoints (telephones) supported. Failing to…

Perform Routine System Administration Tasks

Question

A customer called Avaya Support after their telecom administrator was unable to add 50 new telephones for new hires. Avaya support determined that the number of telephones exceeded the capacity the system could support. Which pre-implementation step was omitted?

Options

  • AAccessing support.avaya.com to verify customer systems compatibility.
  • BTesting all third-party equipment and software.
  • CVerifying that the version installed is compatible with existing versions.
  • DProviding accurate licensing specification.

How the community answered

(45 responses)
  • A
    4% (2)
  • B
    11% (5)
  • C
    7% (3)
  • D
    78% (35)

Explanation

Option D is correct because the root cause of the problem was that the system had a capacity limit the customer unknowingly exceeded - this is a licensing issue. Avaya systems require licenses that specify the maximum number of endpoints (telephones) supported. Failing to provide accurate licensing specifications before deployment means the system was provisioned without enough capacity for the planned 50 new phones.

Why the distractors are wrong:

  • A is about compatibility verification on Avaya's support portal, which relates to software/hardware compatibility - not capacity limits.
  • B concerns third-party equipment testing, which is irrelevant since the issue was internal system capacity, not external hardware.
  • C addresses version compatibility between installed components - again a compatibility concern, not a capacity/licensing one.

Memory tip: Think of licenses as "seats at the table." If you don't specify how many seats you need before the event, guests will be left standing. Whenever a system refuses to add more devices, think licensing capacity, not compatibility.

Topics

#Licensing Specifications#System Capacity Planning#Pre-implementation Procedures#System Administration

Community Discussion

No community discussion yet for this question.

Full 72201T Practice