- A
Configuring who can access company mailboxes and administrative roles.
Identity and access configuration is usually the customer’s responsibility in SaaS. The company must decide who gets access, what roles they receive, and how privileges are approved.
- B
Applying security patches to the provider's mail servers.
Why wrong: In SaaS, the provider patches and maintains the underlying service infrastructure. Customers do not normally manage the provider’s server patching or platform maintenance.
- C
Deciding what data may be stored in the service and how it is classified.
Data governance remains with the customer even in SaaS. The organization still decides what content belongs in the service, how sensitive it is, and what handling rules apply.
- D
Replacing failed provider storage disks.
Why wrong: Hardware maintenance is part of the provider’s responsibility in SaaS. The customer should not expect to repair or replace the provider’s physical components.
- E
Hardening the provider's hypervisor.
Why wrong: The provider manages the platform stack underneath the service. Customers normally focus on account settings, data handling, and usage policy rather than hypervisor hardening.
SY0-701 Security Architecture Practice Question
This SY0-701 practice question tests your understanding of security architecture. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 uses a SaaS email platform. The provider manages the servers and application code. Which two tasks remain the company's responsibility? Select two.
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
Configuring who can access company mailboxes and administrative roles.
Option A is correct because in a SaaS model, the customer retains administrative control over user access and role-based permissions. This includes configuring mailbox permissions, setting up multi-factor authentication, and managing administrative roles within the provider's interface. The provider handles the underlying infrastructure, but identity and access management (IAM) remains the customer's responsibility.
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.
- ✓
Configuring who can access company mailboxes and administrative roles.
Why this is correct
Identity and access configuration is usually the customer’s responsibility in SaaS. The company must decide who gets access, what roles they receive, and how privileges are approved.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Applying security patches to the provider's mail servers.
Why it's wrong here
In SaaS, the provider patches and maintains the underlying service infrastructure. Customers do not normally manage the provider’s server patching or platform maintenance.
- ✓
Deciding what data may be stored in the service and how it is classified.
Why this is correct
Data governance remains with the customer even in SaaS. The organization still decides what content belongs in the service, how sensitive it is, and what handling rules apply.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Replacing failed provider storage disks.
Why it's wrong here
Hardware maintenance is part of the provider’s responsibility in SaaS. The customer should not expect to repair or replace the provider’s physical components.
- ✗
Hardening the provider's hypervisor.
Why it's wrong here
The provider manages the platform stack underneath the service. Customers normally focus on account settings, data handling, and usage policy rather than hypervisor hardening.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that 'patching' is always the customer's job, but in SaaS the provider handles all infrastructure patching, while the customer's responsibility is limited to configuration and data governance.
Detailed technical explanation
How to think about this question
Under the shared responsibility model for SaaS (e.g., Microsoft 365, Google Workspace), the provider secures the physical hosts, network, and application code, while the customer manages data classification, user access policies, and compliance configurations. For example, the customer must configure Azure AD or Google Cloud Directory roles and set data loss prevention (DLP) rules, but cannot modify the hypervisor or mail server OS. This aligns with NIST SP 800-145 and cloud security alliance guidelines.
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 security team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.
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: Configuring who can access company mailboxes and administrative roles. — Option A is correct because in a SaaS model, the customer retains administrative control over user access and role-based permissions. This includes configuring mailbox permissions, setting up multi-factor authentication, and managing administrative roles within the provider's interface. The provider handles the underlying infrastructure, but identity and access management (IAM) remains the customer's responsibility.
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.
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.