SAP-C02 Question #457: Real Exam Question with Answer & Explanation

Question

A company has an IoT platform that runs in an on-premises environment. The platform consists of a server that connects to IoT devices by using the MQTT protocol. The platform collects telemetry data from the devices at least once every 5 minutes. The platform also stores device metadata in a MongoDB cluster. An application that is installed on an on-premises machine runs periodic jobs to aggregate and transform the telemetry and device metadata. The application creates reports that users view by using another web application that runs on the same on-premises machine. The periodic jobs take 120-600 seconds to run. However, the web application is always running. The company is moving the platform to AWS and must reduce the operational overhead of the stack. Which combination of steps will meet these requirements with the LEAST operational overhead? (Choose three.)

Options

• AUse AWS Lambda functions to connect to the IoT devices
• BConfigure the IoT devices to publish to AWS IoT Core
• CWrite the metadata to a self-managed MongoDB database on an Amazon EC2 instance
• DWrite the metadata to Amazon DocumentDB (with MongoDB compatibility)
• EUse AWS Step Functions state machines with AWS Lambda tasks to prepare the reports and to
• FUse an Amazon Elastic Kubernetes Service (Amazon EKS) cluster with Amazon EC2 instances

Explanation

B, D, and E represent the lowest-overhead path to AWS by replacing each on-premises component with its fully managed equivalent: AWS IoT Core natively handles MQTT device connections without managing a broker server; Amazon DocumentDB provides MongoDB-compatible storage as a fully managed service; and AWS Step Functions with Lambda handles the periodic jobs (120–600 seconds) serverlessly - well within Lambda's 15-minute limit - eliminating the need for a continuously running on-premises machine for batch work.

Why the distractors fail:

• A is wrong because Lambda cannot maintain persistent MQTT connections - it's stateless and event-driven; IoT Core is the correct managed MQTT endpoint.
• C increases rather than reduces overhead - self-managed MongoDB on EC2 still requires patching, backups, and cluster maintenance, which DocumentDB handles for you.
• F (EKS + EC2) introduces substantial operational overhead (node groups, cluster upgrades, networking) that is completely unnecessary for a simple periodic batch workload.

Memory tip: For "least operational overhead" questions, map each component to its fully managed AWS equivalent - IoT broker → IoT Core, MongoDB → DocumentDB, cron jobs → Step Functions + Lambda. Any answer that keeps you managing servers (EC2, EKS with EC2 nodes, self-managed databases) is almost always wrong.

No community discussion yet for this question.