- A
Use HTTPS with a certificate from a trusted certificate authority so users can validate the portal.
HTTPS protects the connection in transit and lets clients validate that they are communicating with the expected portal through trusted certificate chains. That addresses the need to confirm the portal's identity over the network and prevents interception or modification by an attacker on the path.
- B
Use FTP over the internet because the credentialed login keeps the transfer secure enough.
Why wrong: FTP does not provide encryption or strong server identity validation for the data path. Credentials alone do not make the traffic confidential or resistant to interception. Because the scenario requires identity verification and trust in transit, FTP is not an acceptable choice.
- C
Digitally sign the update packages so clients can verify integrity even if the web server is later compromised.
Digital signatures let clients verify that the package was created by a trusted publisher and has not changed since it was signed. Even if the web server is compromised, attackers cannot forge a valid signature without the private key. This protects the authenticity and integrity of the update itself.
- D
Publish a SHA-256 hash on the same download page and trust that the server will remain honest.
Why wrong: A hash posted on the same server is only useful if the server is trustworthy at the moment the user checks it. If the web server is compromised, an attacker can replace both the file and the hash. A standalone hash does not provide the same tamper resistance as a digital signature.
- E
Use plain HTTP and rely on file permissions to protect the updates in transit.
Why wrong: File permissions protect storage on the server, not the network path between the server and the user. Plain HTTP offers no confidentiality or identity validation, so an attacker could modify or intercept the package. The scenario specifically requires secure transmission and trust even if the server is later compromised.
Quick Answer
The answer is to use HTTPS with a trusted certificate authority (CA) and to digitally sign the update packages. HTTPS provides server identity validation by allowing the client to verify the certificate’s chain of trust and domain match, which prevents man-in-the-middle attacks during the initial connection. Digital signatures ensure update integrity because the signature is created with a private key and verified with a public key, so even if the web server is later compromised, the signed packages remain tamper-proof. On the Security+ SY0-701 exam, this question tests your understanding of defense-in-depth: HTTPS secures the channel, while digital signatures protect the content beyond the channel. A common trap is to think HTTPS alone guarantees package integrity, but it only protects data in transit—once the server is compromised, unsigned updates could be swapped. Memory tip: HTTPS for the handshake, digital signatures for the payload—trust the channel, then trust the file.
SY0-701 Security Architecture Practice Question
This SY0-701 practice question tests your understanding of security architecture. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company distributes update packages through a web portal. Users must verify the portal's identity over the network, and the downloaded packages must be trusted even if the web server is later compromised. Which two controls best satisfy these goals? Select two.
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"best"Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Use HTTPS with a certificate from a trusted certificate authority so users can validate the portal.
HTTPS with a certificate from a trusted certificate authority (CA) allows the client to validate the web portal's identity by verifying the certificate's chain of trust and ensuring the domain name matches. This prevents man-in-the-middle attacks and confirms the server is legitimate before any data is exchanged.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use HTTPS with a certificate from a trusted certificate authority so users can validate the portal.
Why this is correct
HTTPS protects the connection in transit and lets clients validate that they are communicating with the expected portal through trusted certificate chains. That addresses the need to confirm the portal's identity over the network and prevents interception or modification by an attacker on the path.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use FTP over the internet because the credentialed login keeps the transfer secure enough.
Why it's wrong here
FTP does not provide encryption or strong server identity validation for the data path. Credentials alone do not make the traffic confidential or resistant to interception. Because the scenario requires identity verification and trust in transit, FTP is not an acceptable choice.
- ✓
Digitally sign the update packages so clients can verify integrity even if the web server is later compromised.
Why this is correct
Digital signatures let clients verify that the package was created by a trusted publisher and has not changed since it was signed. Even if the web server is compromised, attackers cannot forge a valid signature without the private key. This protects the authenticity and integrity of the update itself.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Publish a SHA-256 hash on the same download page and trust that the server will remain honest.
Why it's wrong here
A hash posted on the same server is only useful if the server is trustworthy at the moment the user checks it. If the web server is compromised, an attacker can replace both the file and the hash. A standalone hash does not provide the same tamper resistance as a digital signature.
- ✗
Use plain HTTP and rely on file permissions to protect the updates in transit.
Why it's wrong here
File permissions protect storage on the server, not the network path between the server and the user. Plain HTTP offers no confidentiality or identity validation, so an attacker could modify or intercept the package. The scenario specifically requires secure transmission and trust even if the server is later compromised.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think FTP with credentials is sufficient for identity verification, but FTP does not provide certificate-based server authentication, and the question specifically requires verifying the portal's identity over the network, which only HTTPS with a trusted CA certificate achieves.
Trap categories for this question
Scenario analysis trap
FTP does not provide encryption or strong server identity validation for the data path. Credentials alone do not make the traffic confidential or resistant to interception. Because the scenario requires identity verification and trust in transit, FTP is not an acceptable choice.
Detailed technical explanation
How to think about this question
HTTPS uses TLS to encrypt the session, and the server presents an X.509 certificate signed by a trusted CA. The client performs certificate path validation, checks the signature, expiration, and revocation status (via CRL or OCSP) to confirm the server's identity. Digitally signing update packages with a private key (e.g., using RSA or ECDSA) allows clients to verify the signature with the corresponding public key, ensuring integrity and authenticity even if the server is later compromised, because the signature is generated offline and cannot be forged without the private key.
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.
TExam Day Tips
- 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.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Security Architecture — study guide chapter
Learn the concepts, then practise the questions
- →
Security Architecture practice questions
Targeted practice on this topic area only
- →
All SY0-701 questions
1,152 questions across all exam domains
- →
Security+ SY0-701 study guide
Full concept coverage aligned to exam objectives
- →
SY0-701 practice test guide
How to use practice tests most effectively before exam day
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.
General Security Concepts practice questions
Practise SY0-701 questions linked to General Security Concepts.
Threats, Vulnerabilities, and Mitigations practice questions
Practise SY0-701 questions linked to Threats, Vulnerabilities, and Mitigations.
Security Architecture practice questions
Practise SY0-701 questions linked to Security Architecture.
Security Operations practice questions
Practise SY0-701 questions linked to Security Operations.
Security Program Management and Oversight practice questions
Practise SY0-701 questions linked to Security Program Management and Oversight.
Security+ social engineering questions
Practise SY0-701 questions linked to Security+ social engineering questions.
Security+ cryptography practice questions
Practise SY0-701 questions linked to Security+ cryptography.
Security+ IAM questions
Practise SY0-701 questions linked to Security+ IAM questions.
Security+ risk management questions
Practise SY0-701 questions linked to Security+ risk management questions.
Security+ incident response questions
Practise SY0-701 questions linked to Security+ incident response questions.
Security+ malware questions
Practise SY0-701 questions linked to Security+ malware questions.
Security+ vulnerability management questions
Practise SY0-701 questions linked to Security+ vulnerability management questions.
Practice this exam
Start a free SY0-701 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SY0-701 question test?
Security Architecture — This question tests Security Architecture — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use HTTPS with a certificate from a trusted certificate authority so users can validate the portal. — HTTPS with a certificate from a trusted certificate authority (CA) allows the client to validate the web portal's identity by verifying the certificate's chain of trust and ensuring the domain name matches. This prevents man-in-the-middle attacks and confirms the server is legitimate before any data is exchanged.
What should I do if I get this SY0-701 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This SY0-701 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SY0-701 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.