All practice questions

2232 questions

Question 61Question

A security engineer conducts an architecture review of a hypervisor cluster hosting mission-critical enterprise workloads. The assessment reveals that the Out-of-Band (OOB) Baseboard Management Controller (BMC) interfaces of the physical host servers reside on the same IP subnet as the guest virtual machine data traffic. The organization relies exclusively on the enterprise perimeter firewall to restrict outside access, placing no internal firewall rules, microsegmentation, or access control lists (ACLs) between the guest networks and the BMC interfaces. Which of the following architectural vulnerabilities represents the MOST critical threat to the infrastructure?

Show answer & explanation

Answer: Implicit trust of internal network traffic and reliance on perimeter controls without host management microsegmentation

Answer

Implicit trust of internal network traffic and reliance on perimeter controls without host management microsegmentation represents the most critical architectural vulnerability, as it allows laterally moving attackers inside the network to target out-of-band host management interfaces directly.
Out-of-band host management interfaces (such as BMCs/IPMI) grant full, hardware-level control over server physical infrastructure. Co-locating these sensitive management interfaces on the same subnet as guest workloads creates a severe architectural flaw. Relying exclusively on perimeter firewalls assumes that all internal network traffic is trusted. In a secure architecture, management interfaces must be microsegmented onto dedicated, isolated VLANs with strict host access controls and zero-trust verification.

Step-by-Step Solution

1
Analyze the enterprise architecture scenario described in the stem.
Identified that Baseboard Management Controller (BMC) interfaces share the same broadcast domain and IP subnet as guest virtual machines.
Out-of-band host management interfaces provide low-level control over physical host hardware, power management, and firmware.
2
Evaluate the current defense posture and isolation controls.
The enterprise relies solely on edge perimeter firewalls without internal microsegmentation or VLAN isolation.
If an attacker compromises any guest virtual machine on that subnet, perimeter firewalls offer zero protection against internal lateral movement.
3
Select the option that correctly identifies the root architectural vulnerability and its impact.
The implicit perimeter trust assumption without microsegmentation exposes host hardware controllers to lateral compromise from guest networks.
Proper security architecture mandates out-of-band management interfaces to be isolated on dedicated, strictly controlled management VLANs with Zero Trust access controls.

Key Concept

Host and Network Architecture Vulnerabilities (Perimeter Trust vs. Management Network Microsegmentation)
Question 62Question

Match each vulnerability assessment and security testing method on the left with its appropriate operational description on the right.

Click a left item, then click its matching right item

Items

Credentialed Vulnerability Scan
Passive Vulnerability Monitoring
Dynamic Application Security Testing (DAST)
Static Application Security Testing (SAST)

Matches

Show answer & explanation

Answer

Credentialed Vulnerability Scan pairs with using valid host credentials to inspect internal OS configurations and patches; Passive Vulnerability Monitoring pairs with capturing live network traffic packet streams without sending probes; Dynamic Application Security Testing (DAST) pairs with evaluating a running web application from an external perspective; Static Application Security Testing (SAST) pairs with analyzing uncompiled source code prior to application execution.
The methods align accurately with their operational characteristics: Credentialed scanning uses administrative access for internal system auditing; Passive monitoring sniffs network telemetry without active probing; DAST tests live executing applications externally; SAST analyzes static source code prior to deployment.

Step-by-Step Solution

1
Classify application security testing based on execution state.
Identify that SAST evaluates source code in a static state, whereas DAST requires a deployed, running application.
Execution state dictates whether analysis is conducted inside-out (source code) or outside-in (runtime testing).
2
Distinguish between authenticated system scanning and passive network monitoring.
Recognize that credentialed scans log into endpoints for internal inspection, while passive monitoring sniffs packet headers non-intrusively.
Credential access enables deep host-level configuration auditing, while passive capture avoids generating additional network overhead.

Key Concept

Vulnerability Assessment and Security Testing Methods
Question 63Question

A security analyst is reviewing incident reports to classify different types of malicious software based on their core behavior and primary indicators of compromise. Match each malware type on the left with its corresponding technical indicator or defining behavior on the right.

Click a left item, then click its matching right item

Items

Ransomware
Keylogger
Rootkit
Logic Bomb

Matches

Show answer & explanation

Answer

Ransomware matches file encryption with payment demands; Keylogger matches capturing keystrokes to steal credentials; Rootkit matches modifying kernel routines to conceal processes; Logic Bomb matches remaining dormant until a specific trigger condition occurs.
Each malware type is paired correctly with its defining behavior: Ransomware encrypts data for ransom, Keyloggers record input keystrokes, Rootkits modify OS kernel routines for stealth, and Logic Bombs execute payloads upon specific conditional triggers.

Step-by-Step Solution

1
Analyze Ransomware
Identify that its primary indicator is file encryption paired with a ransom note demanding payment for decryption keys.
Encryption of user files and ransom notifications are unique characteristics of ransomware.
2
Analyze Keylogger
Identify that its primary behavior is recording user input keystrokes.
Keyloggers focus specifically on harvesting input data like passwords and sensitive text.
3
Analyze Rootkit
Identify that its key feature is stealth gained through OS kernel/system file modification.
Rootkits hide presence and maintain administrative control deep within the operating system.
4
Analyze Logic Bomb
Identify that its defining trait is execution triggered by specific pre-defined events or conditions.
Logic bombs lie dormant until a designated trigger activates their payload.

Key Concept

Malware Classification and Telemetry Indicators
Question 64Question

Match each threat actor type to its primary defining attribute or motivation in cybersecurity. Which pairings accurately reflect each threat actor profile?

Click a left item, then click its matching right item

Items

Nation-state actor
Insider threat
Hacktivist
Script kiddie

Matches

Show answer & explanation

Answer

Nation-state actor matches high technical sophistication and geopolitical intent; Insider threat matches authorized access to internal systems; Hacktivist matches ideological or political motivation; Script kiddie matches low technical expertise relying on pre-existing tools.
Nation-state actors possess extensive funding and geopolitical objectives; insider threats hold existing authorized privileges; hacktivists are motivated by social or political causes; and script kiddies operate using unoriginal, pre-packaged exploit kits due to limited technical skills.

Step-by-Step Solution

1
Analyze each threat actor category based on their skill level, access rights, and underlying motivation.
Identified nation-state actors as high-resource entities, insiders as credentialed individuals, hacktivists as ideology-driven actors, and script kiddies as low-skilled tool users.
Distinguishing threat actor attributes is essential for accurate threat modeling and risk assessment.

Key Concept

Threat Actor Characteristics and Attributes
Question 65Question

Match each enterprise security management scenario to the cloud service model that reflects its allocation of customer responsibilities under the Shared Responsibility Model.

Click a left item, then click its matching right item

Items

Managing virtual machine operating system patches, guest firewall rules, and persistent storage volume encryption
Configuring application logic, database access controls, and custom API endpoints while the provider manages runtime binaries
Managing user identity governance, role-based permissions, and data loss prevention policies for a vendor-hosted turn-key application
Securing event-driven execution code and trigger definitions while the provider handles automatic container scaling and host OS management

Matches

Show answer & explanation

Answer

Operating system patching and guest firewall configuration match Infrastructure as a Service (IaaS). Application logic and database access control configuration match Platform as a Service (PaaS). User identity governance and data loss prevention for pre-built applications match Software as a Service (SaaS). Event-driven code execution and trigger definitions match Function as a Service (FaaS).
Each cloud service model defines a distinct boundary of ownership under the Shared Responsibility Model: IaaS grants customer control over guest OS and virtual networking; PaaS isolates customer control to application logic and data schemas; SaaS restricts customer management to user access, data protection, and client devices; and FaaS delegates container scaling and OS maintenance to the provider while the customer provides serverless code functions.

Step-by-Step Solution

1
Analyze the customer control boundary for each administrative task scenario.
Tasks range from low-level OS management to high-level application access governance and serverless trigger setup.
The cloud shared responsibility model dictates customer responsibilities based on the abstraction layer of the chosen service model.
2
Associate lower-level infrastructure administration with compute-focused delivery models.
Guest operating system patching and virtual storage encryption belong to IaaS.
IaaS provides virtualized hardware resources where OS maintenance falls on the tenant.
3
Differentiate application runtime management from ephemeral execution.
Persistent application configuration maps to PaaS, while short-lived event-driven function management maps to FaaS.
PaaS abstracts OS management for hosted application frameworks, whereas FaaS abstracts long-running servers completely.
4
Identify complete vendor-hosted software management.
Turn-key applications where the customer manages only access permissions and data map to SaaS.
SaaS abstracts all infrastructure and software maintenance away from the cloud consumer.

Key Concept

Cloud Shared Responsibility Model across Service Models
Question 66Question

Match each enterprise host, network, or architecture vulnerability scenario to its primary mitigation strategy.

Click a left item, then click its matching right item

Items

Unpatched buffer overflow vulnerability in legacy edge router firmware
Plaintext management protocols (Telnet/HTTP) enabled across core network switches
Flat network architecture allowing unrestricted communication between workstations and database servers
Critical operational technology (OT) host running an End-of-Life (EoL) operating system

Matches

Show answer & explanation

Answer

Unpatched router firmware buffer overflow matches with virtual patching via NIPS; Plaintext switch management protocols match with disabling legacy services and enforcing SSHv2/HTTPS; Flat network architecture matches with re-architecting into segmented VLANs with firewall ACLs; EoL OT operating system matches with isolating the host in a restricted network zone via microsegmentation.
Each vulnerability is paired with its appropriate architectural or technical control: virtual patching defends unpatched firmware via inline NIPS inspection; SSHv2/HTTPS eliminates plaintext credential interception; network segmentation prevents lateral movement in flat topologies; and network isolation mitigates the inherent exposure of unpatchable EoL hosts.

Step-by-Step Solution

1
Analyze the firmware buffer overflow vulnerability on the legacy edge router.
Identify that because immediate software patching or device replacement may be delayed, virtual patching via NIPS signatures provides inline mitigation.
Virtual patching intercepts attack vectors at the network layer without modifying firmware.
2
Evaluate the risk of plaintext management protocols (Telnet/HTTP) on core switches.
Determine that migrating to encrypted management standards (SSHv2 and HTTPS) protects credentials from interception.
Plaintext protocols transmit credentials unencrypted across the network.
3
Assess the security impact of a flat enterprise network topology.
Recognize that dividing the network into segmented VLANs with firewall ACLs restricts lateral movement between compromised end-user nodes and backend databases.
Flat networks lack internal boundaries, exposing internal servers to host compromises elsewhere on the subnet.
4
Determine the risk mitigation for an End-of-Life host operating system.
Apply microsegmentation to isolate the unpatchable legacy host from general enterprise traffic.
EoL systems cannot be patched against new vulnerabilities, so compensating controls must restrict network reachability.

Key Concept

Host, Network, and Architecture Vulnerability Mitigations
Question 67Question

A security analyst is selecting appropriate security assessment methodologies for an enterprise infrastructure audit. Match each vulnerability assessment and security testing method on the left to its corresponding operational characteristic on the right.

Click a left item, then click its matching right item

Items

Credentialed Vulnerability Scanning
Static Application Security Testing (SAST)
Dynamic Application Security Testing (DAST)
Passive Infrastructure Monitoring

Matches

Show answer & explanation

Answer

Credentialed Vulnerability Scanning matches authenticated local access inspection; Static Application Security Testing (SAST) matches non-running source code evaluation; Dynamic Application Security Testing (DAST) matches runtime black-box executing application testing; Passive Infrastructure Monitoring matches non-intrusive traffic telemetry capture.
Each vulnerability assessment method is accurately paired with its core function: Credentialed Vulnerability Scanning uses privileged system logins to audit internal configurations and patch statuses; SAST evaluates source code in a non-running state; DAST probes functional applications during runtime from an external perspective; and Passive Infrastructure Monitoring observes network traffic without sending active probes.

Step-by-Step Solution

1
Categorize each methodology by execution state and access level.
Identify whether the testing method evaluates code offline, probes running application endpoints, uses privileged host credentials, or observes network traffic passively.
Security assessment techniques differ fundamentally based on whether they require administrative access, access to source code, active application execution, or packet sniffing capabilities.
2
Pair application security testing techniques (SAST and DAST) to their development phase and testing perspective.
SAST matches non-running source code evaluation (white-box/offline), while DAST matches black-box testing of an executing runtime application.
SAST analyzes static code logic during development, whereas DAST injects payloads into live running web services.
3
Pair infrastructure assessment techniques (Credentialed Scanning and Passive Monitoring) to their probing behavior.
Credentialed scanning matches authenticated host configuration and patch inspection, while passive monitoring matches non-intrusive traffic telemetry capture.
Credentialed scanning uses system privileges to log into endpoints directly, whereas passive monitoring observes traffic without transmitting active network packets.

Key Concept

Vulnerability Assessment and Security Testing Methods
Estimated Time:2m 0s
Question 68Question

Match each cloud service model to the primary component managed by the enterprise customer under the cloud shared responsibility model.

Click a left item, then click its matching right item

Items

Infrastructure as a Service (IaaS)
Platform as a Service (PaaS)
Software as a Service (SaaS)

Matches

Show answer & explanation

Answer

Infrastructure as a Service (IaaS) matches guest operating system maintenance, installed application stacks, and virtual network security settings; Platform as a Service (PaaS) matches application source code and stored data; Software as a Service (SaaS) matches user credential management and data access permissions.
Each cloud service model defines clear boundaries for the shared responsibility model: IaaS requires customer configuration of guest operating systems and virtual networks; PaaS limits customer responsibility to application code and data management; SaaS restricts customer management strictly to user authentication and data access controls.

Step-by-Step Solution

1
Determine customer responsibilities for Infrastructure as a Service (IaaS).
IaaS leaves operating system management, virtual networking, and application security to the customer.
The provider only maintains physical servers, facilities, and the hypervisor layer.
2
Determine customer responsibilities for Platform as a Service (PaaS).
PaaS limits customer control to deployed application code and data.
The provider handles operating system administration, runtime environments, and database engines.
3
Determine customer responsibilities for Software as a Service (SaaS).
SaaS leaves user credentials and data access policies as the primary customer responsibilities.
The provider operates and secures the full application software stack.

Key Concept

Cloud Shared Responsibility Model across IaaS, PaaS, and SaaS service models.
Question 69Question

A security analyst is investigating severe performance slowdowns on a server transferring large archive files across the network. The investigation reveals that the file transfer service uses RSA asymmetric encryption to encrypt the full content of every file being transmitted, rather than using it solely to negotiate a symmetric session key. Which of the following describes the fundamental cryptographic weakness causing this performance issue?

Show answer & explanation

Answer: Improper selection of asymmetric encryption for bulk data transport instead of symmetric algorithms

Answer

Improper selection of asymmetric encryption for bulk data transport instead of symmetric algorithms
Asymmetric encryption algorithms (such as RSA) require complex mathematical calculations that consume heavy processing power, making them inefficient for encrypting large amounts of data. Standard security architecture uses hybrid encryption, where asymmetric cryptography safely exchanges a symmetric session key, and a fast symmetric cipher (such as AES) encrypts the bulk file payload.

Step-by-Step Solution

1
Identify the operational impact and technical cause described in the scenario
The server experiences heavy CPU load due to encrypting large file payloads with RSA asymmetric encryption.
Asymmetric encryption relies on computationally intensive modular exponentiation.
2
Compare cryptographic algorithm use cases
Symmetric encryption algorithms (e.g., AES) are designed for high-speed bulk data protection, whereas asymmetric algorithms (e.g., RSA) are intended for key exchange, digital signatures, and small payloads.
Hybrid cryptosystems use asymmetric encryption only to exchange a symmetric key, which then encrypts the bulk data.
3
Select the option that correctly identifies the cryptographic weakness
Using asymmetric algorithms directly for bulk data encryption is the root cause of performance degradation.
Correct alignment of algorithm type to payload size is essential for system efficiency and security.

Key Concept

Asymmetric vs. Symmetric Encryption Application in Hybrid Cryptosystems
Question 70Question

A security analyst is reviewing endpoint telemetry and forensic artifacts across several compromised systems. Match each malware classification on the left with its corresponding technical indicator of compromise (IoC) or behavior on the right.

Click a left item, then click its matching right item

Items

Kernel-Mode Rootkit
Fileless Malware
Logic Bomb
User-Space Keylogger

Matches

Show answer & explanation

Answer

Kernel-Mode Rootkit matches SSDT modification to hide processes; Fileless Malware matches executing payload directly in memory via VirtualAllocEx without disk artifacts; Logic Bomb matches dormant malicious script triggered by a specific event condition; User-Space Keylogger matches API hooking via SetWindowsHookEx with WH_KEYBOARD_LL.
Each malware classification is accurately paired with its distinct technical telemetry indicator: Kernel-mode rootkits manipulate kernel structures like SSDT; Fileless malware runs in memory using native process injection APIs without disk files; Logic bombs await specific logical condition triggers; Keyloggers register keyboard hooks like SetWindowsHookEx.

Step-by-Step Solution

1
Analyze telemetry indicating system-level modification and stealth mechanisms.
Identify that SSDT manipulation at the OS kernel level is characteristic of Kernel-Mode Rootkits.
Rootkits aim to maintain persistent access while cloaking their presence from monitoring tools via kernel hooking.
2
Evaluate memory-only execution signatures without file system footprint.
Correlate VirtualAllocEx injection into legitimate host processes to Fileless Malware.
Fileless malware avoids detection by traditional antivirus by running strictly in memory.
3
Identify event-driven execution triggers embedded in dormant code.
Associate conditional execution based on database changes or user actions with a Logic Bomb.
Logic bombs execute malicious code only when specific logical conditions are satisfied.
4
Examine input event interception telemetry.
Match SetWindowsHookEx keyboard hooking API calls to a User-Space Keylogger.
Keyloggers require mechanisms to intercept and record user inputs across applications.

Key Concept

Identifying Malware Types via Technical Telemetry and Indicators of Compromise (IoCs)
Question 71Question

During a comprehensive security audit following a series of distinct security events across a global enterprise, threat intelligence analysts are categorizing observed activities by threat actor type, attributes, and primary attack vectors. Match each threat actor profile on the left with the enterprise scenario on the right that best exemplifies its characteristic capabilities, motivation, and attack vector.

Click a left item, then click its matching right item

Items

Organized Crime Syndicate
Malicious Insider
Shadow IT / Unintentional Insider
Nation-State Advanced Persistent Threat (APT)

Matches

Show answer & explanation

Answer

Organized Crime Syndicate matches the double-extortion ransomware deployment; Malicious Insider matches the exfiltration of proprietary files using legitimate credentials following a passed-over promotion; Shadow IT / Unintentional Insider matches the unauthorized transmission of databases into an unvetted public cloud AI service; Nation-State APT matches the custom zero-day exploits and Living-off-the-Land persistence.
The correct pairings accurately map threat actor attributes to realistic attack vectors: Organized Crime Syndicate matches the financial extortion ransomware scenario; Malicious Insider matches authorized access abuse driven by internal grievance; Shadow IT / Unintentional Insider matches unsanctioned cloud tool adoption for business tasks; and Nation-State APT matches stealthy, highly sophisticated zero-day and LotL techniques for strategic persistence.

Step-by-Step Solution

1
Analyze threat actor motivations and sophistication levels
Identify financial intent for criminal syndicates, internal access/grievance for insiders, convenience/lack of policy awareness for unintentional actors, and stealth/strategic advantage for nation-states.
Threat actor attributes directly influence their choice of targets, tools, and vectors.
2
Evaluate attack vectors and operational indicators for each scenario
Ransomware and RaaS correlate to organized crime; authorized access abuse correlates to malicious insiders; unsanctioned SaaS usage correlates to shadow IT; zero-days and LotL tactics correlate to nation-state APTs.
Mapping indicators to actor capabilities allows precise classification during threat analysis.
3
Match each actor to its corresponding scenario based on intent, capability, and vector
Pair left_1 with right_2, left_2 with right_1, left_3 with right_3, and left_4 with right_4.
Each pairing represents the defining characteristics of that threat actor profile according to security domain standards.

Key Concept

Threat Actor Attributes, Motivations, and Attack Vectors
Question 72Question

An enterprise security architect is designing compensating controls for legacy operational technology (OT) controllers on an industrial network. The controllers run an end-of-life operating system that cannot be patched or upgraded due to critical vendor warranty constraints. Which TWO of the following technical mitigation techniques should the security architect implement to prevent privilege escalation and lateral movement without impacting system stability? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Implement application allowlisting policies on the host controllers to restrict execution strictly to pre-approved operational binaries and scripts.; Isolate the host controllers within microsegmented network zones using firewalls to limit communications strictly to essential industrial protocols.

Answer

The correct mitigations are implementing application allowlisting on host controllers and isolating the controllers within microsegmented network zones using firewalls.
Application allowlisting and microsegmentation provide robust compensating controls for legacy environments where patching is impossible. Application allowlisting prevents malicious code from running locally to escalate privileges, while microsegmentation restricts lateral movement by limiting network communications strictly to required operational protocols.

Step-by-Step Solution

1
Analyze host constraints and vulnerability risks
Patching is not viable due to legacy OS limitations and vendor warranties, requiring host-based compensating controls that block unauthorized binary execution.
Host security must prevent exploit execution without altering legacy application software.
2
Select execution control mitigation
Application allowlisting ensures only explicitly approved binaries and scripts are permitted to execute.
Allowlisting prevents privilege escalation tools and dropped payloads from running even if vulnerability vectors exist.
3
Select network containment mitigation
Microsegmentation enforces network layer isolation around host controllers.
Restricting communications strictly to necessary industrial control protocols stops lateral movement across network segments.

Key Concept

Enterprise Hardening and Compensating Security Controls for Legacy Systems
Question 73Question

A financial institution maintains its core transactional database within an on-premises data center to strictly observe regulatory data sovereignty mandates. During peak quarterly reporting periods, local compute capacity is insufficient. The security team implements an automated architecture that securely extends non-sensitive processing workloads into a third-party public cloud environment while maintaining dedicated encrypted connectivity back to the private data center. Which cloud deployment model is being utilized in this scenario?

Show answer & explanation

Answer: Hybrid cloud

Answer

The scenario describes a hybrid cloud deployment model utilizing cloud bursting.
A hybrid cloud deployment integrates two or more distinct cloud infrastructures (such as private/on-premises and public cloud) bound together by standardized technology that enables data and application portability. Dynamically expanding local private capacity into public cloud compute during peak demand is known as cloud bursting.

Step-by-Step Solution

1
Analyze the environment components described in the scenario.
Identified an existing on-premises data center operating alongside a third-party public cloud service.
Determining the infrastructure boundaries helps classify the deployment model.
2
Evaluate the workload operational interaction between the environments.
The organization dynamically scales capacity from on-premises into the public cloud for overflow processing (cloud bursting).
Bridging private and public environments to share workloads defines hybrid cloud functionality.

Key Concept

Hybrid Cloud Deployment and Cloud Bursting
Estimated Time:1m 0s
Question 74Question

An incident response team investigates a physical intrusion where an unauthorized cellular bridge was connected inside a financial firm's network distribution room. Reviewing access logs and security footage reveals that an attacker contacted the facilities desk pretending to be an official state electrical inspector. The attacker claimed an imminent safety violation required an emergency inspection of the transfer switches to avoid immediate facility shutdown. Driven by the fear of operational disruption, the staff member generated a temporary badge and granted unescorted access without cross-referencing the official vendor schedule. Which social engineering attack vector and primary principles of influence were combined to execute this breach?

Show answer & explanation

Answer: Pretexting leveraging authority and urgency

Answer

Pretexting leveraging authority and urgency
Pretexting is the technique of establishing a fabricated scenario or identity to trick a victim into disclosing sensitive information or granting unauthorized physical/logical access. The threat actor manipulated human behavior by claiming official inspector status (authority) and warning of immediate power shutdown (urgency), prompting staff to bypass standard identity verification rules.

Step-by-Step Solution

1
Analyze the attack mechanism described in the scenario
Identified that the attacker created a complex invented story (acting as a fake electrical inspector needing emergency access) to trick staff into granting entry.
Creating a fabricated scenario to manipulate a target into providing access or information defines pretexting.
2
Evaluate the psychological principles of influence applied by the threat actor
Recognized that posing as an official inspector appeals to authority, while threatening an immediate facility shutdown creates extreme urgency.
Social engineers leverage authority to compel compliance with perceived figures of power and urgency to rush victims into bypassing standard security verification protocols.
3
Differentiate the correct vector and influence principles from distractors
Ruled out physical piggybacking (tailgating), physical lure placement (baiting), and compromised website drive-bys (watering hole).
The breach relied on direct communication, persona fabrication, and high-pressure compliance demands rather than passive physical entry or technical site compromise.

Key Concept

Pretexting and Psychological Principles of Influence in Social Engineering
Question 75Question

Match each social engineering attack vector to the enterprise incident scenario that best exemplifies its delivery method and tactics.

Click a left item, then click its matching right item

Items

Watering Hole Attack
Voice Phishing (Vishing)
Typosquatting
Baiting

Matches

Show answer & explanation

Answer

Watering Hole Attack matches the compromised industry news portal scenario; Voice Phishing matches the targeted helpdesk phone calls scenario; Typosquatting matches the character substitution domain replica scenario; Baiting matches the malware-laden USB drive parking lot scenario.
Each social engineering vector is uniquely aligned with its underlying vehicle: watering hole targets trusted third-party websites; vishing relies on phone-based social engineering and pretexting; typosquatting targets URL typing mistakes; and baiting exploits curiosity through physical media dropped in accessible areas.

Step-by-Step Solution

1
Analyze the watering hole vector.
Identified that watering hole attacks target websites frequented by a specific organization or demographic to compromise visitors.
Matching to the scenario involving a compromised niche industry news portal frequented by target contractors.
2
Analyze the voice phishing (vishing) vector.
Identified that vishing uses telephony infrastructure to impersonate trusted entities and manipulate victims.
Matching to the scenario involving targeted phone calls to helpdesk staff posing as executives.
3
Analyze the typosquatting vector.
Identified that typosquatting relies on mistyped URLs containing slight character variations.
Matching to the scenario involving a domain registered with subtle character substitutions.
4
Analyze the baiting vector.
Identified that baiting relies on physical or digital promises that entice victims through curiosity or financial incentive.
Matching to the scenario involving USB drives labeled with tempting titles left in a parking lot.

Key Concept

Social Engineering Attack Vectors and Vectors of Influence
Question 76Question

A security analyst investigates an incident where an attacker compromised a containerized microservice pod and used stolen service account credentials to move laterally and extract confidential data from an internal backend database. The current environment relies primarily on an ingress Web Application Firewall (WAF) and perimeter firewalls, which permitted all internal pod-to-pod traffic once the perimeter was traversed. Which of the following technical mitigation strategies should the organization implement to enforce least privilege access and restrict lateral movement within the container environment?

Show answer & explanation

Answer: Implement a service mesh architecture with mutual TLS (mTLS) and explicit identity-based service authorization policies.

Answer

Implementing a service mesh architecture with mutual TLS (mTLS) and explicit identity-based service authorization policies.
The correct strategy involves deploying a service mesh with mutual TLS (mTLS) and explicit service authorization policies. In microservice environments, service mesh controls enforce microsegmentation by authenticating service identities cryptographically via mTLS and enforcing granular policies that block unauthorized pod-to-pod communication, directly stopping lateral movement.

Step-by-Step Solution

1
Analyze the incident scenario and attack vector
Identified that once the perimeter was breached, the attacker performed lateral movement across internal container pods due to lack of internal access controls.
Perimeter controls (WAF/ingress firewalls) do not prevent east-west lateral movement inside a cluster once a single service is compromised.
2
Evaluate enterprise hardening strategies based on Zero Trust principles
Determined that microsegmentation and identity-based access controls are required to restrict inter-service communication.
Zero Trust mandates explicit verification for every request, regardless of whether it originates inside or outside the network boundary.
3
Select the appropriate technical control for containerized microservices
Selected service mesh with mTLS and identity-based authorization rules as the optimal technical mitigation.
Service mesh provides cryptographic identity (via mTLS certificates) to microservices and enforces fine-grained authorization policies to prevent unauthorized lateral traffic.

Key Concept

Enterprise Microsegmentation and Zero Trust Hardening
Question 77Question

A security analyst is investigating anomalous network activity within a corporate VLAN. Systems on the subnet experience intermittent latency, and central syslog feeds capture repeated notifications from the primary switch indicating rapid MAC address movement (flapping) for the default gateway across several access ports. Concurrently, network packet captures reveal that the switch has entered a fail-open state, broadcasting unicast frames meant for specific internal servers out of all physical ports on the VLAN. Which of the following attacks is MOST likely occurring?

Show answer & explanation

Answer: MAC Flooding attack

Answer

The MAC Flooding attack is the correct answer because filling the switch CAM table forces the device into fail-open mode, resulting in unicast traffic flooding and MAC flapping indicators.
The correct answer is MAC Flooding because floods of fake MAC addresses exhaust the switch memory buffer (CAM table). Once full, the switch transitions to a hub-like operational mode (fail-open), forwarding all incoming unicast packets out to every port, which generates MAC flapping alerts for legitimate MAC addresses as bogus frames overwrite table slots.

Step-by-Step Solution

1
Analyze the switch syslog indicators.
Identified rapid MAC address flapping for the default gateway MAC address across multiple physical access ports.
MAC flapping indicates that the switch MAC table is receiving conflicting port binding entries in rapid succession.
2
Evaluate the packet capture behavior.
Observed unicast network traffic being broadcast out of all switch ports on the VLAN.
Switches only broadcast unicast frames to all ports when their Content Addressable Memory (CAM) table memory is exhausted (fail-open state).
3
Correlate symptoms with known network attack signatures.
Confirmed MAC Flooding (CAM Table Overflow) as the unique attack mechanism causing both fail-open unicast flooding and MAC address flapping.
CAM table depletion is the primary diagnostic signature of a MAC flooding attack.

Key Concept

MAC Flooding / CAM Table Overflow Attack Indicators
Question 78Question

During a post-incident investigation, a security analyst discovers that an attacker executed a multi-channel campaign against an organization. First, remote administrators received text messages during a off-hours maintenance window directing them to a fake portal to re-authenticate their multi-factor credentials due to an urgent server outage. Second, the attacker telephoned the helpdesk, impersonated the Chief Information Security Officer, and pressured an technician into bypassing standard identity verification to reset a high-privilege account password immediately. Which of the following social engineering attack vectors and influence principles were demonstrated in this incident? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Smishing leveraging urgency to capture administrative credentials; Vishing leveraging authority to bypass helpdesk verification procedures

Answer

The attack involved smishing leveraging urgency to capture administrative credentials, and vishing leveraging authority to bypass helpdesk verification procedures.
The scenario describes two distinct communication channels: text messaging (SMS) to lure administrators into revealing credentials under time pressure (smishing combined with urgency), and voice phone calls impersonating executive leadership to force policy bypasses (vishing combined with authority).

Step-by-Step Solution

1
Analyze the vector used in the SMS message targeting remote administrators.
Identified SMS-based messaging (smishing) exploiting time sensitivity during off-hours maintenance (urgency).
Phishing via SMS text messaging is classified specifically as smishing.
2
Analyze the vector used in the telephone call to the helpdesk.
Identified voice-based communication (vishing) using executive impersonation (authority).
Phishing over voice telephony is classified specifically as vishing, and posing as CISO leverages senior management hierarchy.

Key Concept

Identification of social engineering attack vectors (Smishing, Vishing) and psychological principles of influence (Urgency, Authority).
Estimated Time:2m 0s
Question 79Question

A threat intelligence team at a global maritime logistics provider is investigating an intrusion into their vessel tracking and scheduling infrastructure. The investigation reveals that an Advanced Persistent Threat (APT) group maintained continuous, undetected access for nine months after obtaining valid third-party vendor API credentials. Forensic analysis indicates the threat actor deployed proprietary, custom-built malware operating exclusively in volatile memory to conduct long-term intelligence gathering. Which TWO of the following attributes and attack vectors typically characterize this specific category of threat actor in contrast to casual hacktivists or script kiddies?

Select all that apply

Show answer & explanation

Answer: High technical sophistication manifested through custom, fileless memory malware engineered to bypass endpoint defenses; Substantial financial and operational resources enabling long-term persistence and stealthy cyber espionage

Answer

The threat actor described is characterized by high technical sophistication utilizing custom in-memory malware and substantial financial and operational resources enabling long-term persistence.
The correct selections accurately identify nation-state APT attributes: high technical sophistication demonstrated by custom fileless in-memory malware and extensive resource funding supporting prolonged, stealthy cyber espionage.

Step-by-Step Solution

1
Analyze the incident scenario indicators
Identified long-term presence (nine months), proprietary memory-only malware, and third-party vendor credential abuse, indicating a nation-state Advanced Persistent Threat (APT).
Threat actor categorization relies on observing intent, capability, sophistication, funding, and attack vectors.
2
Evaluate capability and sophistication characteristics
Developing custom fileless payloads requires high technical sophistication, distinguishing APTs from lower-skilled actors.
Script kiddies and low-tier actors rely on known, off-the-shelf exploit scripts rather than custom memory malware.
3
Evaluate resource levels and motivation attributes
Sustaining a multi-month stealthy cyber espionage campaign requires extensive resource backing and long-term strategic intent.
Hacktivists typically seek short-term public disruption for awareness, whereas nation-states fund stealthy, persistent surveillance.

Key Concept

Threat Actor Attributes and Attack Vectors
Question 80Question

A financial technology firm processes sensitive payment transactions using a serverless architecture (Function-as-a-Service) and utilizes a third-party Software-as-a-Service (SaaS) platform for customer records management. Which of the following security tasks remain the sole responsibility of the enterprise customer across these cloud deployment models? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Developing secure application source code and defining IAM role permissions for the serverless functions.; Classifying organizational data and administering user access rights within the SaaS platform.

Answer

The enterprise customer is strictly responsible for developing secure serverless application code, managing IAM role policies, classifying organizational data, and controlling user access within the SaaS application.
Under the cloud shared responsibility model, higher abstraction models (such as FaaS and SaaS) transfer physical infrastructure, operating system maintenance, and host application management to the cloud provider. However, regardless of the deployment model, the customer always retains ultimate responsibility for data classification, identity and access management (IAM), and custom code development.

Step-by-Step Solution

1
Evaluate customer responsibilities in Function-as-a-Service (FaaS)
In FaaS, the cloud provider abstracts away servers, operating systems, and runtime provisioning. The customer is solely responsible for code security, data handling, and access permissions (IAM).
Understanding the boundary of abstraction in serverless compute models.
2
Evaluate customer responsibilities in Software-as-a-Service (SaaS)
In SaaS, the provider manages the application code, infrastructure, and hardware availability. The customer remains responsible for data governance, classification, user management, and authorization.
Identifying shared responsibility limits in application-level cloud services.
3
Select tasks common to customer ownership
Writing secure code and configuring IAM for serverless functions, alongside classifying data and managing user access in SaaS, fall entirely on the customer.
Matching shared responsibility allocation across abstract cloud service models.

Key Concept

Cloud Shared Responsibility Model across FaaS and SaaS
Estimated Time:1m 30s
PreviousPage 4 / 112Next
All practice questions — CompTIA Security+ | Examkin