In a Cisco Finesse 10.0(x) deployment, which option is needed from the primary and secondary servers for certificate authority to generate a root, intermediate, and application certificate for Cisco…

Question

Options

• Afully qualified domain name of the servers
• Bphysical MAC address of the NIC card from the Cisco Finesse servers
• CCertificate Signing Request
• DIP address of server
• Esystem ID of the server

• B
  2% (1)
• C
  87% (39)
• D
  7% (3)
• E
  4% (2)

Explanation

A Certificate Signing Request (CSR) is the required input from both the primary and secondary Finesse servers because it is the standard PKI mechanism that packages the server's public key and identity information into a structured format that a Certificate Authority (CA) can process to issue signed certificates - without it, the CA has no cryptographic material to work with.

Why the others are wrong:

• A (FQDN): The FQDN may appear inside a CSR as the Common Name, but it is not independently submitted to the CA - the CSR is the delivery vehicle.
• B (MAC address): MAC addresses are Layer 2 hardware identifiers; they play no role whatsoever in PKI or certificate issuance.
• D (IP address): An IP may optionally be included as a Subject Alternative Name within a CSR, but submitting an IP alone gives the CA nothing to sign.
• E (System ID): This is not a concept in PKI workflows and has no relevance to certificate generation.

Memory tip: Think of the CSR as a "passport application" - just as a passport office needs your completed application form (not just your name or address) to issue a passport, the CA needs the CSR (not just server identifiers) to issue certificates.

No community discussion yet for this question.