The correct answer is D, Terms of engagement. In CEH penetration testing methodology, testing must be performed only within the boundaries agreed upon with the client before the assessment begins. The engagement terms define what systems, networks, applications, IP ranges, testing methods, time windows, attack types, and operational limits are authorized. CEH-aligned penetration testing guidance emphasizes that the pre-attack phase includes agreeing on rules of engagement, understanding client requirements, finalizing test scope, and signing contracts before testing begins. It also states that scope should be discussed, reviewed with the customer, and described in writing, including which assets and processes are tested and how testing is performed. PCI-DSS is a payment-card security standard, not a pen-test scope document. A nondisclosure agreement protects confidential information discovered during the test. A memorandum of understanding may describe cooperation between parties but is not the best answer for limiting specific testing activities.
Therefore, the terms of engagement are the document that limits the scope of your activities.

Retrieving directory naming contexts requires a base-level LDAP query that explicitly requests the server's root naming information. Using the base scope with the namingcontexts attribute allows enumeration of the directory's root partitions and structural layout before performing deeper searches against specific organizational units or objects.

https://support.riverbed.com/content/support/software/steelcentral-npm/airpcap.html Since this question refers specifically to analyzing a wireless network, it is obvious that we need an option with AirPcap (Riverbed AirPcap USB-based adapters capture 802.11 wireless traffic for analysis). Since it works with two traffic analyzers SteelCentral Packet Analyzer (Cascade Pilot) or Wireshark, the correct option would be "Wireshark with Airpcap." NOTE: AirPcap adapters no longer available for sale effective January 1, 2018, but a question on this topic may occur on your exam.
=

In CEH-aligned cloud security discussions, protecting data across its lifecycle is a primary requirement, and a major risk area is how data moves between clients, applications, and cloud services. The scenario states the exposure occurred because there was no encryption during transmission between user devices and cloud storage. That maps directly to the Service and Data Integration risk area because it focuses on the security controls applied when cloud services exchange data with users and with other services, including secure communication channels, API protection, and proper cryptographic enforcement for data in transit.
When data is transmitted without TLS or with weak or misconfigured TLS, it becomes vulnerable to interception and manipulation through man in the middle attacks, traffic sniffing, SSL stripping, or downgrade attacks. In regulated environments such as healthcare, HIPAA expectations strongly align with implementing strong encryption in transit and ensuring secure session establishment, certificate validation, and modern cipher suites. This is not primarily a multi tenancy or physical security issue, which relates to isolation between tenants and the provider's datacenter controls. It is also not primarily an incident analysis and forensic support issue, which concerns detection, logging, evidence collection, and investigative capability after events occur. Infrastructure security is broader and can include network protections, but the question is specifically about preventing exposure during transmission, which is most precisely addressed by service and data integration controls.
Correct remediation typically includes enforcing HTTPS with modern TLS, enabling HSTS, disabling legacy protocols and weak ciphers, ensuring correct certificate management, using mutual TLS where appropriate, and securing cloud storage access through authenticated, encrypted endpoints and properly secured APIs.