Exactprep Apprentice Questions

Multi-factor authentication requires two or more different categories of authentication factors. The standard categories are something you know, something you have, and something you are. Answering a security question is something you know, while providing a thumbprint is something you are, so answer A is MFA. Entering a PIN is something you know, while scanning a smart card is something you have, so answer B is also MFA. Scanning the palm of one hand followed by the other hand uses the same factor category twice: biometrics, or something you are. That may be stronger biometric checking, but it is not multi-factor. Answering three sequential security questions also repeats the knowledge factor and therefore remains single-factor authentication. MFA improves identity security because stolen passwords alone are less useful to attackers when another independent proof is required. Strong MFA should use phishing-resistant methods where possible. Reference/topics: Identity Security 7.1.2, single-factor and multifactor authentication.

An exploit is a technique, code path, or attack method that takes advantage of a vulnerability. A buffer overflow attack is an exploit because it abuses improper memory handling to overwrite memory and potentially execute malicious code, crash a process, or alter program behavior. Misconfigured access control is a vulnerability: it is the weakness that may allow unauthorized access. Unpatched software is also a vulnerability because known flaws remain present. An exposed password is a credential exposure or security weakness, not the exploit itself. The distinction is essential: vulnerabilities are conditions, exploits are methods that use those conditions, and attacks are the broader malicious actions performed by threat actors. Defenders reduce exploitability by patching, secure coding, configuration hardening, input validation, exploit prevention, segmentation, and monitoring. Reference/topics: Cybersecurity 1.1, vulnerabilities and exploits; Cybersecurity 1.5, threat prevention practices.

In IaaS, the cloud provider is responsible for securing the physical infrastructure that supports the service, including physical wires, switches, data centers, servers, and foundational hardware. Customers consume virtualized compute, storage, and networking but do not manage the provider’s physical facilities or underlying hardware fabric. API requests between microservices, database queries between application services, and workload traffic to third-party services are customer or application-owner responsibilities because they involve workload architecture, application logic, network policy, identity, and data protection. The shared responsibility model is especially important in IaaS because customers have significant control over operating systems, applications, configurations, and traffic flows. A common mistake is assuming the provider secures everything simply because the workload runs in the cloud. In reality, the provider secures the cloud infrastructure, while the customer secures what they deploy, configure, and expose. Reference/topics: Cloud Security 5.3, shared responsibility model; Cloud Security 5.2, IaaS.

A next-generation firewall and an intrusion prevention system are the strongest choices for securing a data center against network-based threats. An NGFW provides application-aware policy enforcement, traffic inspection, segmentation support, and threat prevention capabilities at network control points. An IPS is designed to inspect traffic inline and block malicious packets before they reach protected systems. IDS technology is useful for monitoring and alerting, but a traditional IDS is normally passive and does not directly prevent traffic from reaching a target. A proxy can mediate certain types of traffic, especially web traffic, but it is not the broadest or most direct answer for data center infrastructure protection against network-based threats. Data centers require controls that can inspect both north-south and east-west traffic, enforce policy, and stop exploit attempts or known malicious patterns. NGFW and IPS capabilities are therefore aligned with preventive infrastructure security. Reference/topics: Network Security 3.2, NGFWs; Cybersecurity 1.5, intrusion prevention systems and firewalls.

Batch 3 — Questions 26–40