What are two roles of a Certificate Authority (CA) in a trusted third-party CA certificate? (Choose two.)

Question

Options

• Ato provide validation of certificate requests
• Bto issue a CA signed Identity certificates
• Cto provide domain validation certificate
• Dto import the root CA certificate to each component
• Eto generate a new Certificate Signing Request (CSR)

• A
  70% (31)
• B
  9% (4)
• D
  16% (7)
• E
  5% (2)

Explanation

A Certificate Authority serves two key functions in a PKI trust model: validating certificate requests (A) - verifying the identity or domain ownership of the requester before signing - and providing domain validation certificates (C), which confirm control of a domain and are one of the core certificate types third-party CAs issue to establish trust.

Why the distractors are wrong:

• B is tempting but misleading - while CAs do sign certificates, "issuing CA-signed Identity certificates" describes the output of a private/internal CA in an enterprise PKI, not the defining role of a trusted third-party CA.
• D is an administrative task performed by the systems administrator on each device or component, not a function the CA itself performs.
• E is the opposite of correct - the applicant generates the CSR and submits it to the CA; the CA never generates the CSR on the requester's behalf.

Memory tip: Think of the CA as a Notary Public - a notary validates your identity (A) and certifies documents (C), but doesn't fill out your forms (E), mail copies to everyone (D), or hand you a notarized version of their own stamp (B). The CA validates, then certifies.

No community discussion yet for this question.