2V0-622 · Question #101
Which keystore would a vSphere Replication administrator use to manually add an additional Certificate Authority certificate?
The correct answer is A. hms-truststore.jks. vSphere Replication uses separate JKS files for trust and identity; the trust store is where CA certificates are manually added.
Question
Which keystore would a vSphere Replication administrator use to manually add an additional Certificate Authority certificate?
Options
- Ahms-truststore.jks
- Bhms-keystore.jks
- Ccertificates.ks
- Dcacerts.ks
How the community answered
(37 responses)- A89% (33)
- B5% (2)
- C3% (1)
- D3% (1)
Why each option
vSphere Replication uses separate JKS files for trust and identity; the trust store is where CA certificates are manually added.
hms-truststore.jks is the Java KeyStore used by the vSphere Replication HMS (Host Management Service) specifically to hold trusted Certificate Authority certificates. When an administrator needs to manually trust an additional CA - for example to satisfy custom PKI requirements - this is the file that must be updated. It is distinct from the keystore that holds the service's own identity certificate.
hms-keystore.jks holds the HMS service's own private key and signed certificate, not trusted CA certificates.
certificates.ks is not a recognized or standard keystore file name in vSphere Replication's trust infrastructure.
cacerts.ks is not a standard vSphere Replication keystore; the JDK default CA store is named cacerts but is not the file administrators use for this task in vSphere Replication.
Concept tested: vSphere Replication HMS trust store CA management
Source: https://docs.vmware.com/en/vSphere-Replication/index.html
Topics
Community Discussion
No community discussion yet for this question.