What are two considerations for PCCE 2K installation? (Choose two.)

Question

Options

• Aadd Router Logger after installing software
• Badd PGs via PG setup after installing the software
• Crun Domain Manager tool, add root, facility, and instance
• Drun Websetup after installing the software
• Eneeds ICM/CCE software installed on all ICM/CCE servers

• A
  3% (1)
• B
  3% (1)
• C
  5% (2)
• D
  89% (34)

Explanation

D and E are correct because PCCE 2K installation has two critical requirements: running Websetup (D) is a mandatory post-installation step that configures web components and completes the environment setup, and all ICM/CCE servers must have ICM/CCE software installed (E) before PCCE-specific configuration can proceed, since PCCE 2K is a packaged solution built on top of the Unified CCE/ICM infrastructure.

Why the distractors are wrong:

• A (Router Logger): There is no post-install step to "add" a Router Logger separately; logging components are handled within the base ICM/CCE installation itself.
• B (PGs via PG setup): Peripheral Gateways in PCCE are configured as part of the packaged deployment process, not added manually via a separate PG setup wizard after installation.
• C (Domain Manager - root/facility/instance): This workflow belongs to traditional standalone ICM/UCCE deployments, not the PCCE packaged model, which uses a different streamlined configuration approach.

Memory tip: Think "WE" - Websetup + Every ICM/CCE server needs software. PCCE may be "packaged," but it still needs its CCE foundation installed everywhere (E), then Websetup ties it all together (D).

No community discussion yet for this question.