You save $69.98
SY0-701 Premium Bundle
- Premium File 1044 Questions & Answers
- Last Update: Nov 18, 2026
- Training Course 167 Lectures
- Study Guide 1003 Pages
You save $69.98
A packet capture shows outbound TLS connections to an unfamiliar address. The dashboard labels them malicious, but host logs show a newly approved backup agent initiating the sessions. What investigation is appropriate?
Packet metadata and host process logs can confirm whether the sessions match the authorized backup workflow. The SOC should inspect certificate trust, destination and volume against deployment documentation. This preserves healthy service while still checking for compromised agent behavior. The backup-job change record and expected destination list can explain legitimate encryption patterns that resemble command-and-control flows.
An elevated network-reputation score is a valid investigation trigger, but it is not definitive proof that the host initiated malicious activity. The approved backup agent provides a plausible competing explanation requiring verification. Immediate reimaging may destroy useful evidence and interrupt recovery operations; the team should correlate destination ownership, process attribution, certificate validation and change records first.
SNI or other visible TLS metadata can describe a requested hostname but may be attacker-controlled and does not establish successful server authentication. An unfamiliar endpoint should be checked against the backup agent’s allowed destinations, certificate chain and observed process. A string in the handshake alone cannot prove whether encrypted traffic was an approved backup session or malicious communication.
An approved software label is relevant but can be imitated or abused, and configuration changes can redirect even legitimate agents. The SOC should still validate destination ownership, certificate identity, transfer sizes and the deployment record before closing the suspicious network finding.
A new business unit needs a document defining organization-wide expectations for encryption. Engineers also need a concrete list of approved algorithms and minimum key sizes. Which distinction is correct?
A policy communicates management intent and mandatory expectations, while a standard can detail approved algorithms, settings and minimum criteria. Their owners and review processes should be clear. The business unit can then align procedures and configurations with the approved requirements. The standard should name who approves deviations, because permitted cryptography is otherwise likely to diverge among product teams.
A flexible implementation choice is reasonable across different platforms, but the company still needs a consistently approved security baseline for cipher selection, minimum strengths and key handling. If each team can choose arbitrary parameters, engineers cannot prove that the organization-wide expectation was met. A technical standard must translate policy into testable minimum requirements.
Engineers need access to the standards that govern their work. Access may be controlled if a document contains sensitive detail, but hiding all implementation criteria would create inconsistent controls. The standard's function is to guide correct implementation.
A broad policy is useful for setting expectations, but the situation calls for consistent technical implementation parameters across the business. An approved standard must define those concrete requirements so one developer’s interpretation of strong encryption does not conflict with another’s.
A company wants staff to know which websites and personal devices are acceptable at work. Its developers separately need mandatory code-review and deployment rules. Which document mapping is best?
Acceptable use governs how users interact with company systems, while SDLC policy addresses secure design, testing, release and maintenance. Separate but coordinated documents help different audiences understand obligations. Exceptions and reviews should follow a controlled governance process. Separate audiences permit the use policy to address everyday behavior while secure-development guidance controls code and release gates.
A broad policy may communicate employee expectations, yet it does not ensure consistent secure development or release controls. Developers need defined mandatory review and deployment criteria with accountable ownership. The appropriate mapping separates acceptable use from the engineering software development lifecycle standards that implement build security.
An acceptable use policy addresses employee behavior and use of organization resources. Filling it with technical deployment steps while omitting its actual subject leaves both audiences poorly served. The company needs clear employee rules and a separate SDLC framework or standard governing software production.
Incident-response playbooks tell responders what to do when events occur. They are not substitutes for standing employee-use policy or secure coding and deployment standards. The two requested requirements should exist before an incident and be maintained by the relevant policy and engineering owners.
An enterprise information security policy has not been approved for five years. Several departments apply conflicting rules, and no one is accountable for exceptions. Who should own policy approval and maintenance?
Enterprise security governance should assign approval authority, content ownership and a review schedule. Delegated teams can maintain standards and manage exception workflows under that authority. Clear accountability allows departments to understand which version is binding. The authorized owner should publish a revision date and exception process so departmental teams know which version applies.
Technical custodians can provide implementation evidence but do not automatically possess authority to accept enterprise-wide policy risk or resolve cross-department conflicts. Governance should name a responsible executive or delegated policy owner and a review and exception process.
Edit access to a document is not the same as formal ownership. Without accountable approval, departments may treat requirements inconsistently. Version control and authority need to be established separately from convenience editing.
A supplier may offer useful baseline templates and technical advice, but it does not ordinarily possess enterprise risk-acceptance authority. The organization must retain accountable approval, exception ownership and review rights, especially when vendor suggestions conflict with internal legal obligations or business priorities.
A hospital's continuity committee defines who may declare a disaster, while operations staff maintain detailed server restoration runbooks. Which governance arrangement is appropriate?
Continuity governance sets authority, criteria and priorities, while operations executes tested restoration steps within those decisions. The committee should review outcomes and hold owners accountable. This separation supports fast, traceable action during patient-care disruptions. Testing should demonstrate that declaration authority and hands-on recovery roles can coordinate during a simulated hospital outage.
Local engineers need clear escalation routes, but enterprise disaster declaration coordinates broad business impact and scarce recovery resources. A single routine restart may not meet that threshold. The hospital should use defined leadership authority and criteria while leaving technical restoration tasks with trained operational teams.
A runbook can define technical checks and restoration steps, but it does not by itself establish management authority or assess clinical and business priorities. Automated failures can be narrower than an enterprise disaster. Leadership needs governance rules and escalation criteria, while operations maintain safe, testable procedures.
Accountable leadership should set priorities and authorizations, but micromanaging each command can delay recovery and place technical decisions with people lacking operational context. Approved runbooks and delegated responders permit timely execution within defined guardrails. The committee should govern the disaster response, not manually operate every host.
An insurance company has a security incident response policy requiring prompt containment and notification. Its SOC uses a detailed malware isolation playbook. What is the best distinction?
Policy sets organizational expectations, governance and requirements such as escalation and notice. A playbook translates those into role-specific actions for malware or other incidents. The two should align and be reviewed when technologies or legal duties change. The policy should also identify who can declare an incident; the playbook should define contacts, evidence-preservation and containment steps.
Runbooks should be updated when tools and evidence-handling steps change, but operational authors cannot silently redefine legal notice deadlines or approved authority. If a procedure reveals a conflict, the policy owner and compliance team must resolve it. The playbook implements incident obligations; it is not an independent source of new governance permissions.
Operational playbooks can contain response contacts and detailed workflow, but an organization-wide policy must establish governance, decision rights and incident obligations. Without approved authority, a technician may execute steps while nobody can declare an incident or approve external notices. Tool inventories cannot substitute for an executive-level policy.
Embedding every tool command in a policy blurs durable corporate obligations with frequently changing vendor procedures. A product-specific runbook needs technical owners, change control and hands-on testing; policy establishes who is authorized and what outcomes are required. A command list in a governance document does not guarantee a maintained executable playbook.
A global company runs Linux servers, Windows laptops and cloud databases. Management wants consistent encryption outcomes without prescribing one product to every team. Which standard is most appropriate?
A cryptographic standard can set security properties and lifecycle requirements across heterogeneous systems. Teams may use different products while meeting approved strength, custody and rotation controls. The standard should include exception handling and change review as platform capabilities evolve. Engineering teams can map individual platform settings to the same standard and document any incompatible legacy system as a reviewable exception.
A high-level policy establishes intent but does not provide the consistent technical criteria requested across heterogeneous systems. Teams could choose outdated algorithms or mishandle keys while claiming compliance. A documented standard should define acceptable cryptographic approaches, validation, access and recovery requirements while allowing implementations suited to each platform.
Product uniformity may simplify some operations but can cause unsupported configurations or force teams to bypass controls on incompatible systems. The stated goal is consistent protection outcomes across Linux, Windows and managed services. A technology-neutral standard with accepted algorithms and key requirements is more effective than a mandatory single vendor.
TLS protects appropriately configured communications, not every state of data or the long-term custody of stored encryption keys. The company needs requirements for data at rest and in transit, cryptographic strength, lifecycle and exception controls. A transport-only rule leaves major security outcomes uncontrolled.
A company onboards new staff from HR records and removes access after termination. Recently HR and IT systems use different employee identifiers, leaving some accounts active. Which procedure is most important?
A lifecycle procedure should map a unique worker identity to each granted account and confirm termination actions completed. Reconciliation detects unmatched systems and failed revocations. The company should track exceptions and regularly verify that departed identities cannot sign in. Reconciliation should confirm that access actually disappears from downstream SaaS and privileged systems when the authoritative record changes.
Manager notices can help trigger offboarding but may omit service accounts, alternate usernames and applications using different identity keys. The mismatch in the scenario persists when accounts cannot be reliably joined to the actual employee record. The company needs a governed identifier crosswalk and reconciliation of every target system, with exceptions escalated.
Human names are not reliable identifiers because duplicates, spelling changes and service aliases can cause mistaken matches. A joiner-mover-leaver workflow needs an authoritative mapping to every target identity and confirmation that access removal succeeded. Replacing structured HR identifiers with informal name matching would perpetuate the orphan-account risk.
Access recertification can detect some stale grants but often operates after the employee has already departed. It is not a substitute for timely, automated or accountable offboarding keyed to a reliable identity map. The system should immediately correlate the HR termination with all associated technical accounts, then use periodic reviews as a supplementary control.
A company operates in several jurisdictions with different notification rules after a personal-data breach. Its global policy currently mandates one universal deadline without considering local law. What governance approach is appropriate?
A global baseline improves consistency but cannot override applicable regional legal duties. Local requirements may have differing triggers, scopes and timing. Compliance and legal owners should maintain a jurisdiction matrix and keep incident response procedures aligned. The exception path must record which regional law differs from the baseline and who approved that data-processing treatment.
Organizational policy does not normally supersede law. Failing to consider actual legal obligations could produce late notices or inadequate responses. The company should obtain appropriate legal interpretation for its operating regions.
Selecting the least stringent rule may violate stricter applicable requirements. Simplicity is not a defense for missing compliance duties. A layered framework can be centrally managed while accounting for local differences.
Informal exception handling can miss legally prescribed notice windows, required recipients and data-subject duties. Global policy should establish a usable baseline and map jurisdictions where more stringent requirements apply. Escalation paths and evidence collection must operate when an incident happens, not begin after external enforcement contact.
A regulator changes security reporting requirements twice in one year. The company reviews its security standard only every five years, leaving published procedures outdated. What governance improvement is most useful?
A change-monitoring process can route new regulations to responsible owners for impact assessment and controlled revisions. It should update procedures and training when necessary. Evidence of review and effective dates helps demonstrate that the organization responded promptly. A review triggered by new law or material architecture changes complements the normal calendar cycle without waiting for the next anniversary.
Annual review can reduce some staleness, but the regulator has already changed requirements twice within one year. A calendar-only cadence may still miss a near-term effective date or revised reporting field. The security standard needs a named owner and an event-driven process triggered by material regulatory notices, with documented rollout to affected teams.
Legal notices provide timely awareness, but an informal email is not a controlled change to approved procedures or reporting templates. Sites may continue following obsolete instructions after reading the message. A responsible document owner should assess scope, update the authoritative standard, validate new reporting workflows and communicate the effective version.
Regional expertise can identify local obligations, but uncoordinated publishing may introduce inconsistent deadlines or fail to address enterprise-wide dependencies. Material regulatory changes should trigger accountable review and documented updates, with central governance and local legal input. The goal is timely adaptation without contradictory instructions.
An executive committee proposes a higher enterprise risk appetite for a new product. The security team can assess controls but has not been authorized to accept the resulting exposure. Which decision process is appropriate?
Appetite expresses how much uncertainty an organization is willing to accept in pursuing goals. Executive governance should consider objectives, constraints and evidence from risk experts. The decision should be recorded and translated into operational thresholds for consistent enforcement. Management should translate that appetite into measurable limits and governance guidance so service teams can apply it consistently.
Technical access does not establish risk-governance authority. A junior administrator may provide information but is not automatically empowered to determine strategic exposure tolerance. Decision rights should be explicit. Technical tool access does not grant enterprise authority to decide how much strategic risk the company is willing to tolerate.
Vulnerability measurements inform a risk decision but do not transfer authority for enterprise appetite to the security operations team. The organization needs a properly empowered governing body to weigh business objectives and potential loss, with security expertise supporting the decision rather than replacing it.
New services can contain vulnerabilities and dependencies before their first outage. Absence of an incident is not proof of zero risk. The committee should make an informed decision in advance.
Please check your mailbox for a message from support@examlabs.com and follow the directions.