mediummultiple choiceObjective-mapped

Exhibit

$ openssl s_client -connect pay.example.net:443 -servername pay.example.net
CONNECTED(00000003)
depth=0 CN = portal.example.net
verify error:num=62:hostname mismatch
verify return:1
---
Certificate chain
 0 s:CN = portal.example.net
   i:CN = Example Issuing CA
   a:PKEY: rsaEncryption, 2048 (bit)
   Not After : May 10 2026
---

Based on the exhibit, users report that the new payment portal opens only after they bypass a browser warning. Which remediation best restores secure access without weakening certificate validation?

Question 1mediummultiple choice
Full question →

Based on the exhibit, users report that the new payment portal opens only after they bypass a browser warning. Which remediation best restores secure access without weakening certificate validation?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Install the same certificate on every client so the browser warning is suppressed.

Client-side certificate installation does not fix a hostname mismatch on the server certificate. It only changes trust on endpoints and can create maintenance problems.

B

Best answer

Reissue the server certificate so the subject or SAN matches pay.example.net and chain it to the trusted CA.

A valid server certificate must match the hostname users are connecting to, and it must chain to a trusted issuing authority. Reissuing the certificate for pay.example.net resolves the mismatch shown in the exhibit while preserving proper certificate validation.

C

Distractor review

Disable certificate name checking in the browser until the certificate expires.

Disabling validation removes an important security check and makes man-in-the-middle attacks easier. It trades away authenticity to hide the symptom.

D

Distractor review

Replace TLS with a shared symmetric key configured on the web server and all users.

A shared symmetric key is not practical for public web access and would not provide the same authentication properties as PKI-based TLS certificates.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Reissue the server certificate so the subject or SAN matches pay.example.net and chain it to the trusted CA. — The exhibit shows a hostname mismatch: the site is accessed as pay.example.net, but the certificate is issued to portal.example.net. The best fix is to reissue the certificate so the subject common name or, preferably, the SAN includes the correct DNS name and the chain remains trusted. That restores secure HTTPS without teaching users to ignore warnings or weakening validation. Why others are wrong: Installing the same certificate on clients does not correct the server identity problem. Disabling hostname checks hides the issue and creates attack risk. Replacing TLS with a shared secret would remove proper server authentication and would not be suitable for a public payment portal.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.