A team of developers created their own CA and started signing certificates for all of their IoT devices. Which action will make the browser accept these certificates?
A.
Install a TLS instead of SSL certificate on the IoT devices.
B.
Set the private keys 1024-bit RSA.
C.
Preload the developer CA on the trusted CA list of the browser.
C is correct:
To obtain and activate its identity certificate, the system’s (website) owner needs to enroll with the CA first. Here’s the process:
- The resource’s RSA key pair (public and private) is generated.
- A certificate signing request (CSR) containing identity information and the public key is delivered to a CA. Identity details can include data such as the system name, the organization to which the system belongs, and location information.
- The CA validates the request.
- The CA generates the system’s certificate, which contains these (or more) fields, as per the X.509 standard:
- Serial Number, Subject, Public Key, Key Usage, Not Before and Not After, Issuer, Signature Algorithm, Signature.
- The certificate is delivered back and installed on a system.
IoT devices most likely have not a browser at all, so C does not sound good. But A sounds bad as well. A or C but it depends on exact wording.
C is better
It cannot be A as TLS and SSL certificates are the same thing. A certificate can be used for both TLS and SSL. Note: I'm not saying that TLS and SSL are the same thing.
upvoted 1 times
...
...
This section is not available anymore. Please use the main Exam Page.350-901 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
lente_kriebels
Highly Voted 1Â year, 10Â months agom0nking
Highly Voted 1Â year, 7Â months agoTeringzooi
Most Recent 9Â months, 1Â week agodesignated
10Â months, 2Â weeks agoQuiShong
1Â year agozzrdxakpbkiswhvsyu
1Â year, 8Â months agoQuiShong
1Â year ago