2V0-621 · Question #100
When importing an existing SSL certificate into vSphere Replication Server, which file format is required?
The correct answer is A. PKCS#12. Importing an existing SSL certificate into vSphere Replication Server requires the PKCS#12 format because it bundles both the certificate and the private key into a single file.
Question
When importing an existing SSL certificate into vSphere Replication Server, which file format is required?
Options
- APKCS#12
- BDER
- CPEM
- DPKCS#7
How the community answered
(61 responses)- A92% (56)
- B2% (1)
- C2% (1)
- D5% (3)
Why each option
Importing an existing SSL certificate into vSphere Replication Server requires the PKCS#12 format because it bundles both the certificate and the private key into a single file.
PKCS#12 (file extension .pfx or .p12) is the only format accepted by vSphere Replication Server for certificate import because it encapsulates the signed certificate, any intermediate CA certificates, and the corresponding private key together, which the appliance needs to replace its SSL identity completely.
DER is a binary encoding format for certificates only and does not contain the private key, so it cannot satisfy the requirement for a complete SSL certificate replacement.
PEM is a base64-encoded certificate format commonly used on Linux systems, but vSphere Replication Server's import wizard requires the PKCS#12 container format, not standalone PEM files.
PKCS#7 is used to bundle certificate chains without private keys and is not supported for SSL certificate import into the vSphere Replication Server appliance.
Concept tested: vSphere Replication Server SSL certificate import format
Source: https://docs.vmware.com/en/vSphere-Replication/8.8/vsphere-replication-administration/GUID-2C5E6C1D-9E6E-4E9E-8E2B-4B6D1F1E1D1A.html
Topics
Community Discussion
No community discussion yet for this question.