nerdexam
Cisco

300-070 · Question #329

What is the correct procedure for implementing call coverage?

The correct answer is C. configure partitions, directory numbers, line groups, hunt lists, hunt pilot. Configuring CUCM hunt groups for call coverage requires a strict prerequisite order where each component depends on the previous one already existing.

Cisco Unified Communications Manager (CUCM)

Question

What is the correct procedure for implementing call coverage?

Options

  • Aconfigure directory numbers, partitions, hunt pilot, hunt list, line groups
  • Bconfigure partitions, line groups, hunt lists, hunt pilot, directory numbers
  • Cconfigure partitions, directory numbers, line groups, hunt lists, hunt pilot
  • Dconfigure partitions, directory numbers, hunt pilot, hunt list, line groups

How the community answered

(26 responses)
  • A
    8% (2)
  • B
    4% (1)
  • C
    88% (23)

Why each option

Configuring CUCM hunt groups for call coverage requires a strict prerequisite order where each component depends on the previous one already existing.

Aconfigure directory numbers, partitions, hunt pilot, hunt list, line groups

This sequence places hunt pilot and hunt list configuration before line groups, which is invalid because a hunt list cannot reference line groups that do not yet exist.

Bconfigure partitions, line groups, hunt lists, hunt pilot, directory numbers

This sequence configures line groups and hunt lists before directory numbers and partitions are established, leaving line groups without valid members to add during configuration.

Cconfigure partitions, directory numbers, line groups, hunt lists, hunt pilotCorrect

The correct sequence is: partitions first (to establish the routing namespace), directory numbers second (assigned within those partitions to phones), line groups third (which aggregate the DNs into a pool), hunt lists fourth (which order and link line groups), and hunt pilot last (the advertised DN that triggers traversal of the hunt list). This order reflects strict object dependencies - each step references objects created in the prior step, so reversing any two steps results in a configuration with unresolvable references.

Dconfigure partitions, directory numbers, hunt pilot, hunt list, line groups

This sequence configures hunt pilot and hunt list before line groups, reversing the dependency order and making it impossible to associate line groups with the hunt list during its creation.

Concept tested: CUCM hunt group call coverage configuration dependency order

Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1/systemConfig/cucm_b_system-configuration-guide-1251/cucm_b_system-configuration-guide-1251_chapter_01000101.html

Topics

#hunt pilot#hunt list#line groups#call coverage

Community Discussion

No community discussion yet for this question.

Full 300-070 Practice