The best answer is B. Directory traversal.
The URLs show attempts to manipulate the filename parameter in order to access sensitive files and directories on the server, especially:
/etc/
/../etc/passwd
/etc/passwd
This is a classic directory traversal attack, also known as path traversal. The attacker is trying to move outside the intended directory structure and access protected operating system files. The reference to /etc/passwd is a common indicator of an attempt to read sensitive files on Unix/Linux systems.
Why the other options are incorrect:
A). Credential replayCredential replay involves reusing captured authentication credentials, which is not what these requests show.
C). Brute-force attackA brute-force attack involves repeated guessing, usually of passwords, keys, or codes.
That is not the behavior shown here.
D). Resource exhaustionResource exhaustion involves overwhelming a system with requests or usage to reduce availability. These examples instead show attempts to access files through manipulated paths.
From a Security+ standpoint, attacks using ../ to escape directories are a well-known example of directory traversal, so B is the correct answer.

Infrastructure as Code (IaC)enables automated provisioning and configuration of infrastructure, making environmentsrepeatable, consistent, and scalable. The ability tobetter manage and replicate configurations (B) ensures that security settings are not missed and reduces misconfigurations.
According to theCompTIA Security+ SY0-701exam objectives underDomain 4.1 (Explain the security implications of different architecture models),IaCprovides the ability to"automatically enforce security controls"and manageconsistent configuration states, reducing human error.
Reference: CompTIA Security+ SY0-701 Objectives, Domain 4.1 - "Infrastructure as Code (IaC):
Standardized deployment, version control, configuration consistency."

When encrypting data, two fundamental drivers of cryptographic strength are the algorithm you choose and the key length you use (which affects brute-force feasibility and overall security margin). The Study Guide emphasizes algorithm selection as a best practice: "First, choose your encryption system wisely... Choose an encryption system with an algorithm in the public domain that has been thoroughly vetted by industry experts." It then highlights key selection/size as another central decision: "You must also select your keys in an appropriate manner. Use a key length that balances your security requirements with performance considerations." These two choices directly affect whether encryption meaningfully protects confidentiality. By contrast, obfuscation, masking, and tokenization are different data-protection techniques (often used to reduce exposure or de-identify data) rather than core encryption-strength parameters. Salting is primarily associated with strengthening password hashing (defending against rainbow table attacks), not selecting encryption primitives
/strength for general data encryption. Therefore, the best two considerations in the context of encryption itself are Algorithms and Key length.
References: Encryption best practices-select vetted algorithms and appropriate key length .

Integrating each SaaS solution with an Identity Provider (IdP) is the most effective way to address the security issue. This approach allows for Single Sign-On (SSO) capabilities, where users can access multiple SaaS applications with a single set of credentials while maintaining strong password policies across all services. It simplifies the user experience and ensures consistent security enforcement across different SaaS platforms.
References =
* CompTIA Security+ SY0-701 Course Content: Domain 05 Security Program Management and Oversight.
* CompTIA Security+ SY0-601 Study Guide: Chapter on Identity and Access Management.

Mobile Device Management (MDM) platforms enforce security policies on mobile devices, including preventing or detecting jailbreaking, which is the act of removing manufacturer restrictions on devices.
Jailbroken devices bypass security protections, allow installation of unauthorized apps, expose system files, and greatly increase risk.
Security+ SY0-701 identifies MDM as a key defense for mobile ecosystems, providing controls such as:
Jailbreak/root detection
Remote wipe
App allow/deny lists
Configuration enforcement
Encryption enforcement
TPM (A) is hardware-based protection unrelated to MDM. Buffer overflow (B) and SQL injection (D) are software coding vulnerabilities not affected by mobile device policy enforcement.
Thus, the correct answer is C: Jailbreaking.