mediummultiple choiceObjective-mapped

Exhibit

Third-Party Security Review Summary

Vendor: BluePeak HR Cloud
Data type: Employee PII and payroll identifiers

Assessment results:
- SOC 2 Type II report: Not available
- Last independent penetration test: 18 months ago
- Breach notification clause: "As soon as practical"
- Data deletion after termination: 180 days
- Subprocessor list: Not maintained
- Admin MFA: Enabled
- Backup encryption: Not documented

Procurement note: Business unit wants to sign this week to meet HR onboarding deadlines.

Based on the exhibit, what should the organization do before approving this SaaS vendor to process employee HR records?

Question 1mediummultiple choice
Full question →

Based on the exhibit, what should the organization do before approving this SaaS vendor to process employee HR records?

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

Approve the vendor now because admin MFA is enabled and the deadline is urgent.

MFA is a positive control, but it does not address the missing assurance items, weak contract language, or undocumented data handling. Urgency alone is not a sufficient reason to skip third-party risk review.

B

Distractor review

Request a formal risk acceptance memo and sign the contract without additional review.

A risk acceptance memo would still leave major due diligence gaps unresolved. The exhibit shows multiple unresolved issues that should be addressed before approval, not simply documented and ignored.

C

Best answer

Require a security addendum and evidence review before onboarding, including notification timelines, deletion terms, subprocessors, and independent testing.

This is the best answer because the exhibit reveals several third-party risk gaps that matter for employee PII: no current independent assurance, vague breach notification, weak retention language, and no maintained subprocessor list. A contract addendum and evidence review provide enforceable expectations and reduce legal, privacy, and operational risk before data is shared.

D

Distractor review

Move the HR data into the vendor environment first and complete the review after production cutover.

This would expose sensitive HR data before the organization has sufficient assurance. Postponing the review until after cutover weakens governance and creates avoidable privacy and compliance risk.

Common exam trap

Common exam trap: OSPF can fail even when IP connectivity looks correct

OSPF neighbour formation depends on matching areas, timers, network type, authentication and passive-interface behaviour. Do not choose an answer only because the devices can ping.

Technical deep dive

How to think about this question

OSPF questions usually test the details that control adjacency and route selection. Read the neighbour state, area, router ID and interface configuration before deciding what is wrong.

KKey Concepts to Remember

  • OSPF neighbours must agree on key parameters.
  • Router ID selection can affect neighbour relationships and LSDB output.
  • OSPF cost influences the preferred path.
  • A route can appear in OSPF information but not become the installed route.

TExam Day Tips

  • Check area mismatch first when OSPF adjacency fails.
  • Review passive interfaces when a network is advertised but no neighbour forms.
  • Use show ip ospf neighbor and show ip route clues carefully.

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?

OSPF neighbours must agree on key parameters.

What is the correct answer to this question?

The correct answer is: Require a security addendum and evidence review before onboarding, including notification timelines, deletion terms, subprocessors, and independent testing. — The organization should not approve the vendor as-is. The exhibit shows missing or weak controls in areas that matter for handling employee PII: no current independent assurance report, vague breach notification language, poor deletion terms, and no maintained subprocessor list. The best governance step is to require a security addendum and verify evidence before onboarding, so the contract and the vendor's controls match the sensitivity of the data. Why others are wrong: Approving the vendor just because MFA exists ignores the broader control gaps and the sensitivity of HR records. A formal risk acceptance memo is not enough when the vendor could still negotiate better terms or provide evidence. Moving data first and reviewing later reverses the proper order of due diligence and creates unnecessary privacy and compliance exposure. The safest choice is to complete review and contract hardening before onboarding.

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.