A SaaS company holds a password-wrapped file that contains a certificate and its private key, ready to import onto a server. Which PKCS flavor is that file?
Select an answer to reveal the explanation.
Short Explanation
A sealed pouch holding both an identification card and a house key is a key store, not an application for a card. You are looking at PKCS#12, password-wrapped for import onto a server. The trap is a certificate request, a cipher suite, or a public DNS text record.
Full Explanation
PKCS#12 is the personal information exchange format used as a key store. It can carry a certificate and the matching private key, and the file in this case is password-wrapped for import onto a server. That is the flavor that delivers both objects together. "PKCS#12, a password-wrapped key store that holds the certificate together with its private key" matches the file. "PKCS#10, a certificate signing request rather than a store of a signed certificate and key" is a request for a certificate and does not import the private key as a store. "A cipher suite name that lists the algorithms chosen for one TLS session" is a handshake result, not a file of keys. "A public DNS TXT record published so an owner can show control of a domain name" is a public name-system string, not key material. Exam caveat: a certificate request is not the bundle you import when the server needs the private key as well. Operational check: confirm the file opens only with the password and that it contains both the certificate and the private key before importing it on the intended server.