nerdexam
EC-Council

312-50V12 · Question #231

As the chief security officer at SecureMobile, you are overseeing the development of a mobile banking application. You are aware of the potential risks of man-in-the-middle (MitM) attacks where an att

The correct answer is B. It should prevent the app from communicating over a network if it detects a rogue access point.. To prevent man-in-the-middle (MitM) attacks from rogue Wi-Fi hotspots, a mobile banking application should implement a feature that prevents communication if such an untrusted access point is detected. This directly counters the threat of attackers intercepting app-server communi

Submitted by kavita_s· Mar 4, 2026Wireless Network, Mobile, IoT, and OT Hacking

Question

As the chief security officer at SecureMobile, you are overseeing the development of a mobile banking application. You are aware of the potential risks of man-in-the-middle (MitM) attacks where an attacker might intercept communication between the app and the bank's servers. Recently, you have learned about a technique used by attackers where they use rogue Wi-Fi hotspots to conduct MitM attacks. To prevent this type of attack, you plan to implement a security feature in the mobile app. What should this feature accomplish?

Options

  • AIt should require two-factor authentication for user logins.
  • BIt should prevent the app from communicating over a network if it detects a rogue access point.
  • CIt should prevent the app from connecting to any unencrypted Wi-Fi networks.
  • DIt should require users to change their password every 30 days.

How the community answered

(25 responses)
  • A
    8% (2)
  • B
    84% (21)
  • C
    4% (1)
  • D
    4% (1)

Why each option

To prevent man-in-the-middle (MitM) attacks from rogue Wi-Fi hotspots, a mobile banking application should implement a feature that prevents communication if such an untrusted access point is detected. This directly counters the threat of attackers intercepting app-server communication.

AIt should require two-factor authentication for user logins.

Two-factor authentication enhances login security by requiring an additional verification factor, but it does not prevent a Man-in-the-Middle attacker from intercepting data communication once a session is established over a rogue Wi-Fi network.

BIt should prevent the app from communicating over a network if it detects a rogue access point.Correct

This feature directly addresses the specific threat of Man-in-the-Middle (MitM) attacks conducted via rogue Wi-Fi hotspots by ensuring the mobile application ceases communication when an untrusted access point is detected. By preventing data transmission over a potentially compromised network, the app protects sensitive user information from interception and misuse.

CIt should prevent the app from connecting to any unencrypted Wi-Fi networks.

While connecting to unencrypted Wi-Fi networks is a security risk, a rogue hotspot can still be configured with encryption (e.g., WPA2) to appear legitimate while still being controlled by an attacker for a MitM attack, making this an insufficient countermeasure.

DIt should require users to change their password every 30 days.

Requiring periodic password changes is a general security hygiene practice aimed at limiting the lifespan of compromised credentials, but it does not directly prevent Man-in-the-Middle attacks where communication is intercepted in real-time over a rogue Wi-Fi network.

Concept tested: Mobile application network security against MitM attacks

Topics

#Mobile app security#MitM attack#Rogue Wi-Fi#Network detection

Community Discussion

No community discussion yet for this question.

Full 312-50V12 Practice