Question 690
For a security control relating to filtered TCP port, which result shows meaningful enforcement rather than intent alone?
- Packet traces show valid handshake completion and matching return traffic for authorized connections.
- Application health telemetry and approved connection tests confirm service availability independently of ping.
- A service inventory and capture show whether the endpoint deliberately rejects that destination port.
- Firewall decisions and permitted-path tests explain why the remote probe cannot establish a state.
Explanation
Correct Answer
D:Filtering or packet loss can prevent a conclusive TCP port-state observation from a remote position; the outcome tests this precise property in the production control. It relates to the original observation that a probe to a specific port receives no response while other ports on the same host reply.
Incorrect Answers
A:TCP establishes state through a handshake before transferring reliable bidirectional application data; that evidence is relevant when a connection trace shows SYN, SYN-ACK, and ACK before application data flows, but does not establish closure of the filtered TCP port exposure.
B:Echo-response filtering can hide ping responses without proving that the host or its services are offline; that evidence is relevant when a monitored host does not answer ping but its approved application endpoint still accepts connections, but does not establish closure of the filtered TCP port exposure.
C:A reset typically signals a rejected or nonexistent TCP connection, which differs from silent filtering; that evidence is relevant when a probe receives an immediate RST from a reachable address rather than a service welcome banner, but does not establish closure of the filtered TCP port exposure.
Question 691
Which statement is most consistent with the actual behavior of malicious macro attachment?
- Ransomware disrupts data availability through unauthorized encryption or extortion-related destruction.
- Worms can spread automatically through vulnerable network paths without needing a human to launch each copy.
- Static indicators are brittle when malware is repackaged; behaviors can generalize across variants.
- Viruses reproduce by infecting host files and normally rely on execution to spread infection.
- Macro-enabled documents can execute code when users permit active scripting in untrusted files.
Explanation
Correct Answer
E:A document asks recipients to enable active content to view a supposedly routine invoice; that situation illustrates the actual operating behavior under review. Its practical safeguard is to disable untrusted document macros and isolate high-risk attachments from routine workflows, with confirmation when a controlled test attachment cannot execute macros under the applied document policy.
Incorrect Answers
A:Multiple files become unreadable while a process issues large volumes of unexpected rewrite operations; those details characterize ransomware encryption event and would call for isolate affected systems promptly and maintain offline immutable recoverable backups, rather than explaining malicious macro attachment.
B:Infected hosts begin transmitting infection attempts to neighboring machines without user-opened attachments; those details characterize self-propagating worm and would call for patch exposed network services and isolate infected subnets to interrupt propagation, rather than explaining malicious macro attachment.
C:A threat hunt misses a changed malicious binary because the alert relies exclusively on one file hash; those details characterize malware indicator limitations and would call for combine indicators with behavior detection and investigation context rather than relying on hashes alone, rather than explaining malicious macro attachment.
D:A malicious program inserts its code into other executable files that later run on the same host; those details characterize file-infecting virus and would call for use integrity monitoring and protected software distribution to prevent execution of infected binaries, rather than explaining malicious macro attachment.
Question 692
The security owner reviews this situation: An old file-transfer service exposes a directory listing to a user without authentication. What is the most suitable targeted safeguard?
- Inventory service identities, avoid excessive privileges, and use robust managed credentials.
- Separate public DNS data from private records and review externally published names.
- Disable unnecessary anonymous directory searches and scope read permissions to approved identities.
- Disable public anonymous access unless the published data is expressly intended for unrestricted release.
Explanation
Correct Answer
D:Anonymous FTP can publish files and names without identity verification or transport encryption; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that unauthenticated listing requests cannot enumerate private directories on the file-transfer service.
Incorrect Answers
A:Service principal names map services to accounts and can indicate privileged service account exposure; the proposed safeguard addresses a case where a directory assessment reveals service principal names linked to high-value application identities, rather than the anonymous FTP listing finding described here.
B:DNS records may expose system naming and topology when public and internal views are mixed; the proposed safeguard addresses a case where an external reviewer learns internal-looking DNS names from a public-facing name service, rather than the anonymous FTP listing finding described here.
C:LDAP directory reads can disclose identity structure when anonymous search rights are too broad; the proposed safeguard addresses a case where a directory service returns user and group details to an unauthenticated client connection, rather than the anonymous FTP listing finding described here.
Question 693
In a security workshop about blind injection inference, which technical statement is valid?
- Parameter binding separates query structure from untrusted values, preventing data from becoming SQL syntax.
- Excessive database privileges magnify the effect of application bugs or injection attempts.
- Blind SQL injection can reveal information through application behavior or timing even when direct query output is hidden.
- Correlated query diagnostics can expose attempted injection and vulnerable code paths without storing sensitive input unnecessarily.
Explanation
Correct Answer
C:A test environment shows response differences based on conditional database behavior without displaying SQL errors; that situation illustrates the actual operating behavior under review. Its practical safeguard is to remove injection flaws using parameter binding and ensure consistent error handling, with confirmation when approved regression checks show input variations cannot alter query logic or leak conditional truth states.
Incorrect Answers
A:An application builds database queries by concatenating search text into the SQL statement itself; those details characterize parameterized SQL execution and would call for use prepared statements with bound parameters for user-supplied values, rather than explaining blind injection inference.
B:A read-only reporting feature connects to the database with an account allowed to modify all tables; those details characterize database least privilege and would call for grant only necessary SELECT rights to reporting identities and isolate administrative functions, rather than explaining blind injection inference.
D:A monitoring team sees unusual query errors and changing SQL shapes tied to one client endpoint; those details characterize database injection telemetry and would call for monitor abnormal database errors and parameterization failures while remediating vulnerable endpoints, rather than explaining blind injection inference.
Question 694
To confirm effective security handling of dom-based cross-site scripting, which result should an analyst prioritize?
- Malformed serialized input is rejected before dangerous object constructors or methods are invoked.
- Saved hostile test strings render as inert text or safe markup for every viewing role.
- Instrumented browser tests show untrusted fragment data displayed without creating active markup.
- Controlled request strings appear escaped in the reflected response and do not run as browser code.
Explanation
Correct Answer
C:DOM XSS arises when client-side code sends attacker-controlled values into dangerous browser sinks; the outcome tests this precise property in the production control. It relates to the original observation that a browser script copies a URL fragment into innerHTML without a round trip through the server.
Incorrect Answers
A:Deserialization of untrusted object graphs can trigger unsafe code paths or unexpected property changes; that evidence is relevant when an application reconstructs complex server objects directly from untrusted client-supplied serialized data, but does not establish closure of the dom-based cross-site scripting exposure.
B:Stored XSS persists attacker-controlled content server-side and executes when it is later rendered unsafely; that evidence is relevant when untrusted comment content executes in other users' browsers when a discussion page renders saved posts, but does not establish closure of the dom-based cross-site scripting exposure.
D:Reflected XSS occurs when request-derived content is immediately returned without suitable output encoding; that evidence is relevant when a query value is copied into an HTML response and interpreted by the browser as executable markup, but does not establish closure of the dom-based cross-site scripting exposure.
Question 695
Which statement is most consistent with the actual behavior of patch regression validation?
- Compensating safeguards lower exposure when the primary fix is temporarily infeasible without removing the defect.
- A false positive reports a weakness that is not actually present on the assessed asset.
- Container images carry dependency and OS-package vulnerabilities into deployed workloads.
- Security patch completion requires both removal of the defect and preservation of required functionality.
- Third-party transitive dependencies can introduce vulnerabilities independently of directly written code.
Explanation
Correct Answer
D:After a patch deployment, the vulnerable version disappears but the application fails its normal health check; that situation illustrates the actual operating behavior under review. Its practical safeguard is to reassess vulnerability state and run targeted operational regression checks after deployment, with confirmation when version evidence shows the fix is installed and application smoke tests still pass.
Incorrect Answers
A:An obsolete appliance cannot be patched immediately, but traffic to its management service can be limited; those details characterize compensating control and would call for apply restrictive access controls and a time-bound, approved remediation exception, rather than explaining patch regression validation.
B:A scan flags vulnerable software, but a signed vendor inventory shows the affected component is not installed; those details characterize scanner false positive and would call for validate scanner claims against authoritative configurations and document disposition with evidence, rather than explaining patch regression validation.
C:A deployment inherits outdated operating-system packages from an unmaintained base container image; those details characterize container image vulnerability and would call for pin trusted maintained base images and scan artifacts during build and release, rather than explaining patch regression validation.
E:A web application bundles a library with a known flaw even though the application code was not changed; those details characterize software dependency risk and would call for use software composition analysis and update affected dependency paths through controlled builds, rather than explaining patch regression validation.
Question 696
A system owner needs a response to this observation: A network researcher needs to distinguish an organization's routed address prefixes from a vendor's hosting range. Which step directly meets the need?
- Revoke exposed tokens, remove excessive access, and add secret scanning to development workflows.
- Review PTR naming for unintended system details and maintain accurate operational records.
- Use registry-supported RDAP endpoints and respect redaction of personal contact fields.
- Coordinate with the partner to remove excessive disclosures and limit shared identifiers.
- Reconcile public routing ownership with the authorized assessment scope before probing addresses.
- Keep published mail-routing records accurate and retire obsolete mail exchangers.
Explanation
Correct Answer
E:Autonomous system registration and routing information connect public prefixes with network operators; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that the approved prefix list maps each network range to a verified owner or explicit third-party exclusion.
Incorrect Answers
A:Repository history and forks can preserve accidentally committed secrets beyond the current branch; the proposed safeguard addresses a case where a company name appears in a public repository containing a committed configuration file with an API token, rather than the ASN ownership mapping finding described here.
B:PTR records provide reverse address-to-name mapping, which may not mirror forward DNS perfectly; the proposed safeguard addresses a case where a network analyst wants the published hostname associated with an IP address rather than its forward address, rather than the ASN ownership mapping finding described here.
C:RDAP provides structured registration data over HTTPS with access controls and standardized responses; the proposed safeguard addresses a case where an asset owner wants standardized registration records for a domain without relying on old free-form WHOIS formatting, rather than the ASN ownership mapping finding described here.
D:Supply-chain footprints include information published by service providers outside the main organization's domain; the proposed safeguard addresses a case where a public partner portal lists customer organization names and private service references, rather than the ASN ownership mapping finding described here.
F:MX records designate inbound mail exchanges and their relative delivery priorities; the proposed safeguard addresses a case where a mail delivery investigation needs to identify which hosts accept messages for the organization's domain, rather than the ASN ownership mapping finding described here.
Question 697
A trainee confuses several related concepts with NetBIOS name disclosure. Which explanation resolves that confusion?
- LDAP directory reads can disclose identity structure when anonymous search rights are too broad.
- Legacy SNMP community strings act as weak shared access tokens, especially without encryption.
- Legacy NetBIOS name services can leak host inventory and administrative naming conventions.
- DNS records may expose system naming and topology when public and internal views are mixed.
Explanation
Correct Answer
C:A legacy Windows segment reveals workstation names and workgroup identifiers through name-service responses; that situation illustrates the actual operating behavior under review. Its practical safeguard is to disable unnecessary legacy name resolution and filter it across security boundaries, with confirmation when boundary captures show legacy name queries are not answered by protected internal endpoints.
Incorrect Answers
A:A directory service returns user and group details to an unauthenticated client connection; those details characterize anonymous LDAP bind and would call for disable unnecessary anonymous directory searches and scope read permissions to approved identities, rather than explaining NetBIOS name disclosure.
B:A network device exposes interface and configuration information through a shared default community string; those details characterize SNMP default communities and would call for use SNMPv3 authenticated encryption and limit permitted management stations, rather than explaining NetBIOS name disclosure.
D:An external reviewer learns internal-looking DNS names from a public-facing name service; those details characterize DNS service enumeration and would call for separate public DNS data from private records and review externally published names, rather than explaining NetBIOS name disclosure.
Question 698
A trainee confuses several related concepts with stateful firewall tracking. Which explanation resolves that confusion?
- Stateful filtering remembers connection context so established responses can be handled differently from new flows.
- Echo-response filtering can hide ping responses without proving that the host or its services are offline.
- Directional and stateless access rules must account for both request and response traffic.
- TCP establishes state through a handshake before transferring reliable bidirectional application data.
Explanation
Correct Answer
A:A firewall permits return traffic for a permitted outbound connection without a broad inbound rule; that situation illustrates the actual operating behavior under review. Its practical safeguard is to define narrowly scoped outbound initiation rules and inspect state-table behavior for returns, with confirmation when connection-state records associate allowed return packets with their permitted initiating sessions.
Incorrect Answers
B:A monitored host does not answer ping but its approved application endpoint still accepts connections; those details characterize ICMP echo filtering and would call for confirm liveness through an authorized service check rather than treating missing echo replies as proof of absence, rather than explaining stateful firewall tracking.
C:An inbound permit appears correct but replies still fail because an egress rule blocks the return path; those details characterize network acl direction and would call for review source and destination flows and ensure the required reverse path is explicitly allowed, rather than explaining stateful firewall tracking.
D:A connection trace shows SYN, SYN-ACK, and ACK before application data flows; those details characterize TCP three-way handshake and would call for inspect handshake completion and firewall state when diagnosing failed TCP sessions, rather than explaining stateful firewall tracking.
Question 699
A single approved remediation review covers 2 separately named requirements: (1) Dynamic SQL identifier safety; (2) Blind injection inference. Which audit outcomes would directly demonstrate protection for those areas? Choose TWO.
- Approved regression checks show input variations cannot alter query logic or leak conditional truth states.
- Permission tests show the reporting account cannot alter schema or modify unrelated records.
- Requests for unknown sort columns are rejected and permitted columns map to fixed known identifiers.
- Alert tests associate suspicious SQL error spikes with the responsible API route and incident workflow.
- Source review and regression tests show raw query paths no longer concatenate untrusted input.
Explanation
Correct Answers
A:This verifies the blind injection inference component alongside dynamic SQL identifier safety in the combined audit: blind SQL injection can reveal information through application behavior or timing even when direct query output is hidden. For the dynamic SQL identifier safety audit set, the relevant observed case is that a test environment shows response differences based on conditional database behavior without displaying SQL errors.
C:This verifies the dynamic SQL identifier safety component alongside dynamic SQL identifier safety in the combined audit: SQL parameters generally bind values, not arbitrary identifiers such as table or column names. For the dynamic SQL identifier safety audit set, the relevant observed case is that an application lets a user choose a sort column and attempts to pass the column name as a value parameter.
Incorrect Answers
B:Excessive database privileges magnify the effect of application bugs or injection attempts; this result is evidence about database least privilege when a read-only reporting feature connects to the database with an account allowed to modify all tables, not a direct closure test for the named blind injection inference, dynamic SQL identifier safety requirements.
D:Correlated query diagnostics can expose attempted injection and vulnerable code paths without storing sensitive input unnecessarily; this result is evidence about database injection telemetry when a monitoring team sees unusual query errors and changing SQL shapes tied to one client endpoint, not a direct closure test for the named blind injection inference, dynamic SQL identifier safety requirements.
E:An ORM protects only operations that actually use safe parameter binding or validated query construction; this result is evidence about ORM parameter misconception when a developer assumes all ORM operations are injection-safe despite calling a raw query method with string interpolation, not a direct closure test for the named blind injection inference, dynamic SQL identifier safety requirements.
Question 700
The scope-approved analysis reports: An application accepts any server certificate while connecting to its financial API. Which issue or method is primarily illustrated?
- Mobile permission minimization
- Mobile TLS trust bypass
- Insecure mobile storage
- Enterprise mobile work profile
Explanation
Correct Answer
B:Disabling TLS certificate validation enables impersonation even when the connection uses encryption; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to enforce platform certificate trust checks and appropriate endpoint identity validation, verified when the app refuses test servers with untrusted or mismatched certificates during connection setup.
Incorrect Answers
A:Mobile platform permissions restrict sensitive APIs, but users and administrators still must assess necessity; this different classification would fit when a flashlight app asks for microphone, contact, and precise-location access without a relevant feature, not the evidence pointing to mobile TLS trust bypass in the question.
C:Locally stored credentials are exposed if applications use unsafe storage locations or logging behavior; this different classification would fit when a mobile app stores persistent authentication tokens as plaintext in a world-readable debug file, not the evidence pointing to mobile TLS trust bypass in the question.
D:Managed work containers separate enterprise data and policies from personal applications where supported; this different classification would fit when an employer wants to remove corporate email from a personally owned phone without erasing family photos, not the evidence pointing to mobile TLS trust bypass in the question.