In a Cisco Finesse 10.0(x) deployment, which two certificates do the Cisco Finesse primary and secondary servers accept when HTTPS protocol is used to access the administration console or agent…

Question

Options

• Adigital certificate
• Bcertificate authority certificate
• Cdomain validation certificate
• Dself-signed certificate
• Eroot certificate

• A
  8% (4)
• B
  71% (35)
• C
  16% (8)
• E
  4% (2)

Explanation

In Cisco Finesse 10.0(x), servers ship with a self-signed certificate (D) by default, which can be used as-is (though browsers will warn users). For production environments, administrators replace it with a certificate authority certificate (B) - one signed by a trusted CA (like DigiCert or an internal enterprise CA) - to eliminate browser warnings and establish trusted HTTPS connections.

The distractors fail for these reasons: A (digital certificate) is not a distinct type - all certificates are digital, making this too broad to be a meaningful category in Finesse's cert model. C (domain validation certificate) is a commercial SSL/TLS product tier (DV vs. OV vs. EV), not a certificate type that Finesse documentation recognizes as a distinct acceptance category. E (root certificate) is the top-level anchor in a trust chain and lives in the trust store, not something a Finesse server presents to incoming connections.

Memory tip: Think "CA or Self" - Finesse accepts either a trusted outsider (CA certificate) or a self-vouching certificate (self-signed). If it requires a third party (root, domain validation) or is just a vague label (digital), it's a distractor.

No community discussion yet for this question.