That’s right, it would be useful to find out more about the software needed. Amira replies, explaining that the screens would show a number of things: A map of the airport terminal with hot spots that can be tapped on for more detail, such as the gates, for example. Commonly needed directions for the restrooms, cafes, lost luggage and check-in areas. In times of emergency, the screens would direct customers to meeting points. Each one would have a “Call for help” button for anyone in distress or feeling ill. Each kiosk would be unique so that our staff could identify which call for help was pressed and receive an alert on their tablets. Maybe a game for the kids at quiet times. What question should you ask next?

The correct answer focuses on content management and application delivery, which are critical considerations for interactive kiosks. Understanding how frequently content changes (e.g., gate assignments, emergency updates) directly impacts the chosen solution for content delivery and updates. Asking about the specific app needed addresses the software development or selection required to display the described features (maps, directions, emergency alerts, games). "What about transferring configurations to new devices with a pre-programmed NFC tag?" is less relevant at this stage as it focuses on device provisioning, not the core functionality and content. "Are you sure you need kiosks to streamline the experience? Tablets might be cheaper." is dismissive and prematurely questions the client's chosen solution without gathering more information, which is unhelpful in a discovery phase.