// PATH EXAM

🎓 Fundamentals: how it works

8 questions; you pass with 6. It is graded on the server and you will only see your score. If you pass, you can issue your certificate. Review the path first

1. What does a recursive DNS resolver do when the answer is not in its cache? It asks, in order, the root, the TLD server and the domain’s authoritative server It makes up an answer It checks the server’s own hosts file and gives up It asks the browser

2. In TLS, what is the server certificate for? To directly encrypt all the session data To prove the public key belongs to that domain, signed by a trusted authority To choose the port To compress the connection

3. What is Base64? A reversible, keyless encoding: anyone can decode it A digital signature A secure encryption A hash

4. When you sign in to another site "with Google" (OpenID Connect), what does that site receive? Full access to your Gmail Always your phone number An identity token signed by Google that says who you are, without your password Your Google password

5. In TLS 1.3, how is the key that encrypts the session agreed? It is inside the certificate It is a fixed key per domain The client sends it encrypted with the server’s RSA key With an ephemeral Diffie-Hellman exchange: both sides compute the same key without sending it

6. Which DNS record says which servers receive a domain’s mail? MX AAAA TXT CNAME

7. What is a man-in-the-middle (MitM) attack? Someone who sits between two parties to read or alter what they say A brute-force attack on passwords A virus hiding on the disk An email with a malicious attachment

8. Why is the HTTPS padlock not enough to know a website is legitimate? Because it only works on mobile Because anyone can get a certificate for their own domain: the padlock says the connection is encrypted with that domain, not that it is trustworthy Because all certificates are fake Because HTTPS encrypts nothing