What are two ways the agent SSO functions in the ECE/CCE environment? (Choose two.)

Question

Options

• AUnified CCE agents configured for SSO in Unified CCE can now access the ECE gadget in Cisco
• BSS0 allows administrators to check the status of agent and supervisor performance.
• CSS0 is not enabled by default; configuration is necessary.
• DSS0 allows agents, supervisors, and administrators to provide CCE credentials once and be
• EUnified CCE agents who are not configured for SSO in Unified CCE are not allowed to access the

• A
  80% (12)
• B
  7% (1)
• C
  13% (2)

Explanation

Option A is correct because SSO integration between Unified CCE and ECE means agents already configured for SSO in Unified CCE can seamlessly access the ECE gadget (typically within Cisco Finesse) without a separate login prompt. Option D is correct because it captures the fundamental purpose of SSO - agents, supervisors, and administrators authenticate once using their CCE credentials and gain access across integrated systems without re-entering credentials.

Option B is wrong because performance monitoring and status checking are functions of reporting/supervisory tools (like Unified Intelligence Center), not SSO - SSO is purely an authentication mechanism. Option C is wrong because while SSO does require configuration, that describes a setup prerequisite, not a way SSO functions - the question is asking about behavior and capability, not deployment steps. Option E is wrong because it describes an access restriction rather than a functional behavior of SSO, and it conflates the consequence of not being configured with the actual operation of the feature.

Memory tip: Think of SSO as a "one key, many doors" system - the two exam-worthy functions are (1) who gets in (configured CCE agents access ECE gadgets - A) and (2) how they get in (one credential set for everything - D). Anything about monitoring, prerequisites, or restrictions is a distractor.

No community discussion yet for this question.