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 water-treatment facility installs remote-management software from a contractor. The installer includes a library from an unmaintained third-party repository, and the binary's provenance cannot be established. Which exposure is most relevant?
Third-party components may be compromised, vulnerable or unsupported even when distributed inside an apparently legitimate installer. Validating signatures, software bills of materials, hash provenance and approved versions reduces uncertainty before OT deployment. The facility should isolate testing and review supplier maintenance commitments before granting remote-management privileges.
Untrusted dependencies can introduce software defects or malicious behavior, but a valve malfunction is not inevitable from library provenance alone. The plant must assess deployment paths and safety impact rather than asserting an incident without evidence. Precaution is justified without exaggerating current consequences.
A signed installer can establish who distributed the final package and whether the bytes changed after signing; it cannot prove an unknown dependency is maintained or free of malicious code before the signing step. The plant needs dependency inventory, component provenance and testing. Signing is useful but not a substitute for supply-chain assurance.
Software libraries execute with application privileges and can introduce exploitable flaws or intentionally malicious behavior. Origin and maintenance are security-relevant facts, not solely performance concerns. Ignoring the source would bypass necessary supplier and artifact assurance.
A retailer's payment service negotiates an outdated TLS version despite modern certificates. At another site a database encryption key is written to an unprotected shared folder. Which statement correctly distinguishes the vulnerabilities?
Negotiating obsolete TLS is a transport configuration weakness that calls for controlled minimum-version policy and compatibility testing. Exposed key files compromise secrecy regardless of the strength of the encryption algorithm. The team should harden both boundaries and assess whether accessible keys require immediate rotation and data re-encryption.
Certificates help authenticate endpoints and support key exchange but do not by themselves guarantee the negotiated protocol meets current security policy. A stolen key also remains a risk with a valid certificate. The two problems require different controls and evidence.
This reverses the actual failure modes. Storing a secret in a world-readable share can expose encrypted data, while negotiating weak TLS permits outdated transport protection. Neither is primarily physical access based on the observations provided.
Algorithm strength cannot compensate for disclosure of the secret decryption key; anyone possessing a usable key may decrypt protected data. The outdated transport negotiation is a separate issue involving allowed protocol versions, so the retailer should not treat either cryptographic label as a guarantee against the observed exposures.
A deployment pipeline builds a customer-support service from source code. A developer committed a production API credential directly into a public configuration file, and that credential is copied into every container image. What is the main weakness?
A credential in source or an image can be copied by anyone with artifact access and may persist across revisions and caches. The team should revoke the exposed secret, remove it from build history where feasible, and use managed runtime secret delivery. Merely deleting the latest line does not eliminate already distributed keys.
Container packaging does not inherently require exposing secrets or removing authentication. The flaw is how the application receives credentials during build and deployment. Containers can use scoped identities and external secret managers when correctly configured.
Build-agent privileges are a legitimate security concern, but the scenario directly identifies a sensitive API token committed in a public configuration and replicated into every image. Tightening CI permissions alone would not revoke that exposed secret or remove it from distributed artifacts; runtime secret handling is required.
The absence of observed misuse does not make a live secret embedded in public source and distributed images safe. An attacker may copy it without immediately using it, and available logs can be incomplete. The team should treat the credential as exposed, rotate or revoke it, and fix build-time secret handling rather than waiting for a confirmed compromise.
A bank employee installs an Android application package from a forum instead of the approved enterprise store. The package requests accessibility and notification permissions unrelated to its stated purpose. Which risk is most directly increased?
Side loading bypasses some distribution review and device-management safeguards. Accessibility services can be particularly sensitive when misused to observe or interact with applications. The bank should examine permissions, device compliance and installed application provenance before allowing sensitive account workflows. Quarantine the app until it passes enterprise analysis and approval.
Untrusted installation and unusual permissions warrant investigation but do not establish that a named malware family is already present. Confirmation needs behavior, file indicators or trusted analysis. Overstated attribution is less useful than documenting the actual unreviewed software exposure.
A VPN may protect packets between a managed device and an approved gateway, but it does not validate the app publisher, inspect its code or remove privileges granted to that app. Accessibility and notification services can expose on-device content even when traffic is encrypted. The bank needs app approval and permission controls in addition to transport protection.
Permission prompts do not establish developer authenticity, malware screening or business authorization. Accessibility and notification access can be powerful capabilities, and a sideloaded package from an unvetted forum lacks the distribution controls the organization expected for its managed devices.
A manufacturing supplier allows managed mobile devices to access engineering files. One phone is jailbroken, and a user argues that endpoint management enrollment guarantees the phone still has a trustworthy baseline. Which finding is most appropriate?
Management enrollment is one signal, not a guarantee that the platform has remained in an approved state. Root or jailbreak status can reduce the reliability of isolation, integrity and update assumptions. Conditional access should consider current compliance evidence and restrict sensitive engineering files until the device is remediated.
Jailbreaking typically relaxes security restrictions and may allow untrusted modifications rather than ensuring updates are applied. Some changes can undermine code-signing and sandbox protections. There is no basis for treating the altered state as automatically better maintained than the vendor baseline.
Device state is dynamic; enrollment can predate compromise or unauthorized modification. A policy must verify ongoing security posture rather than assume the original registration cannot become stale. A jailbroken state directly challenges the trust expected of the managed baseline.
An enrollment record shows that a device registered with management at a particular point in time, not that altered operating-system protections remain effective. Jailbreaking can weaken sandboxing and enforcement, so ongoing compliance signals and conditional access must reassess the device’s current state.
A hospital vendor confirms an unknown vulnerability in a legacy file-transfer service and has not produced a patch. Researchers publish a proof-of-concept, but the hospital finds no local attack indicators. How should the issue be classified?
The absence of a vendor patch makes the defect an urgent risk-management concern; the term zero-day is appropriate when the flaw is newly undisclosed or unknown to the vendor when exploited/disclosed, not a synonym for every old unpatched bug. The hospital should validate actual exposure and implement interim controls without inventing local compromise evidence.
Availability of exploit code elevates urgency and can increase likelihood, but it does not demonstrate the code was used against this specific server. Confirmation requires host, network or application evidence. The hospital should reduce exposure and hunt for indicators without presenting a hypothesis as an observed incident.
An authenticated path reduces some exposure but does not eliminate risk from compromised accounts, malicious insiders or misconfigured VPN permissions. The flaw remains unpatched and the proof-of-concept is available. Access restrictions can form part of a time-bound mitigation plan, not a declaration that the weakness no longer matters.
A certificate rotation can repair a specific key or trust problem but does not patch unrelated application logic or memory-safety vulnerabilities. The vendor has confirmed a service flaw that remains unfixed. The hospital must address the affected code path and reachable attack surface while investigating for signs of exploitation.
A university course-enrollment API returns confidential student records when a caller supplies a numeric student ID. The endpoint accepts anonymous requests, and the portal must still let authenticated staff view records within their assigned scope. Which change MOST directly addresses the exposure?
The API must establish the caller’s identity and check that the requested student record falls within that principal’s granted role or relationship. Those checks should be enforced on each resource request, rather than accepting a guessed identifier. Logging denied and permitted access helps detect enumeration and audit inappropriate access without exposing records to anonymous clients.
Rate limiting and logs can reduce scraping volume and reveal abuse, but they do not establish who is authorized to read a particular student record. An anonymous user could still obtain confidential data with a small number of requests. The missing security property is access enforcement, not simply protection against high request rates.
Gateway authentication identifies a requester, but it does not authorize that requester for every student record. A logged-in student or low-privilege service could enumerate other users’ data if object-level checks remain absent. The API must verify the requesting principal’s permissions for each specified record, not only at session establishment.
Source-network filtering can provide an additional barrier, but campus addresses can include guest devices, compromised hosts and unrelated students. IP location is not a reliable substitute for verified identity or record-level permissions. The university needs authenticated access decisions at the API/resource boundary even for requests originating from its own network.
A public-agency data center discovers that a batch of replacement network cards has unrecognized firmware identifiers. Purchase orders and shipping records show three intermediaries. What investigation best determines supply-chain exposure?
Component identifiers, authorized firmware hashes, tamper-evident records and each custody transfer can reveal where trust was lost. The agency should quarantine suspect cards while comparing them with manufacturer attestations and known-good samples. Provenance checks are warranted without declaring that malicious firmware is already confirmed. Preserve the serial numbers and chain-of-custody evidence for a defensible supplier review.
A trusted spot check and delivery documentation are useful initial controls, but one sampled card does not establish that every device in a mixed batch has the expected firmware. The unrecognized identifiers and several intermediaries require device-level provenance and manufacturer verification before introducing suspect cards to a trusted network. A substitution could affect only part of the shipment.
A valid purchase order is useful procurement evidence but cannot establish that firmware on each delivered card matches an authorized manufacturer image. The unrecognized identifiers and multiple intermediaries call for provenance and integrity checks before the devices are added to a trusted network.
A downstream custody declaration can account for part of the route, but it cannot validate firmware origin or transformations before that distributor received the parts. The unexplained identifiers remain unresolved. A credible investigation correlates serials, approved firmware measurements and custody events through the full chain, rather than treating one participant’s statement as comprehensive evidence.
A remote-support provider unintentionally exposes an internal administrative dashboard on the internet after a firewall rule change. Code review finds no application bug, and the same binary was safe behind the approved gateway. Which issue best explains the new exposure?
The firewall change removed the expected network restriction, widening the dashboard's audience without changing its code. The team should restore approved source limitations, verify authentication and review logs for improper access during exposure. That addresses the observed failure without inventing a software defect. Changes should be verified from both trusted and untrusted network locations.
A buffer overflow requires memory-handling evidence, not simply a reachable dashboard. Nothing in the scenario establishes overwritten memory or an unsafe parser. The configuration-change history offers a more direct explanation for why previously restricted access became public.
An internet address makes an application reachable but does not prove exploitation of an unknown software flaw. A zero-day claim would require a novel vulnerability and exploit evidence. Here the service became exposed after a known policy change, making configuration the supported cause.
Unexpected reachability may expose an otherwise unchanged application to new threats without proving that its code contains an exploitable defect. The known change was a permissive firewall rule, and the same binary had been safe behind the gateway, so configuration is the supported cause.
A logistics hub notices thousands of office files being rewritten with unfamiliar extensions in minutes. Endpoint logs show one process opening many files and performing cryptographic operations; the user reports a demand for payment. What is the strongest incident classification?
Ransomware commonly encrypts accessible files and may rename them to enforce payment leverage. The observed file access sequence and extortion message support that classification. Responders should contain the affected endpoint, preserve volatile evidence and assess lateral spread before considering restoration from known-good backups. File change events can help reconstruct the attack timeline and affected shares.
Deduplication may change how blocks are stored internally but usually preserves accessible file content and does not demand payment. The combination of rapid renaming, unusable files and an extortion message is inconsistent with an ordinary storage optimization job. The hub should not dismiss destructive behavior as routine maintenance.
Legitimate programs can use cryptographic libraries, so one library call alone would be ambiguous. However, widespread file inaccessibility and a ransom demand provide stronger context. Treating all cryptographic execution as harmless ignores multiple corroborating indicators of active malicious transformation.
Password spraying attempts a small number of passwords across many accounts, typically leaving authentication failures and sometimes lockouts. It does not explain local mass file encryption. Login telemetry could be investigated independently, but the presented file activity describes a different attack.
An industrial site detects a new executable running under a vendor-looking filename. It periodically sends browser-stored credentials outward but leaves documents readable. Which malware behavior fits best?
A Trojan can appear legitimate while performing unauthorized credential collection and exfiltration. Readable files do not rule out serious compromise, but they weaken an encryption-ransomware conclusion. The site should isolate the process, investigate persistence and reset exposed credentials through controlled channels after understanding what data was accessed.
A worm replicates across hosts or services without each new installation needing the same direct user action. One periodic outbound connection demonstrates communication, not autonomous spread. The team would need infection propagation evidence before assigning the worm classification.
Cryptographic erasure or ransomware encryption would render targeted files unavailable or useless without keys, which the scenario expressly does not show. Credential extraction is a confidentiality and identity risk of a different kind. Describing it as file destruction would lead to the wrong immediate response priorities.
Backup jobs should have known owners, schedules, destinations and permissions. A disguised executable transmitting browser secrets to an unapproved endpoint is not ordinary recovery activity. File availability does not establish that the process is authorized or safe.
Please check your mailbox for a message from support@examlabs.com and follow the directions.