nerdexam
Amazon

SAP-C02 · Question #802

A company is migrating its on-premises file transfer solution to AWS Transfer Family. The current system includes an SFTP server, a transformation application, and a messaging server. Transformations

The correct answer is C. Use Amazon S3 as storage with AWS Glue triggered by S3 events for transformations, and notify. This solution uses Amazon S3 as native storage for AWS Transfer Family, triggering serverless AWS Glue jobs via S3 events for immediate transformations, and Amazon SNS for notifications, significantly reducing operational overhead.

Submitted by ashley.k· Mar 6, 2026Migrate Workloads and Modernize Solutions

Question

A company is migrating its on-premises file transfer solution to AWS Transfer Family. The current system includes an SFTP server, a transformation application, and a messaging server. Transformations run every 5 minutes and notify the messaging server when complete. The company wants to simplify and reduce operational overhead. Which solution best meets these requirements?

Options

  • AUse Amazon EFS and a cron job to perform the transformations. Notify using SNS.
  • BUse Amazon EMR to perform the transformations and notify via SNS.
  • CUse Amazon S3 as storage with AWS Glue triggered by S3 events for transformations, and notify
  • DUse Amazon EFS with a time-based AWS Glue job every 5 minutes.

How the community answered

(45 responses)
  • A
    16% (7)
  • B
    9% (4)
  • C
    73% (33)
  • D
    2% (1)

Why each option

This solution uses Amazon S3 as native storage for AWS Transfer Family, triggering serverless AWS Glue jobs via S3 events for immediate transformations, and Amazon SNS for notifications, significantly reducing operational overhead.

AUse Amazon EFS and a cron job to perform the transformations. Notify using SNS.

Using Amazon EFS and a cron job for transformations reintroduces polling instead of event-driven processing, increasing complexity and operational overhead compared to S3 event triggers.

BUse Amazon EMR to perform the transformations and notify via SNS.

Amazon EMR is a big data processing service that is often overkill and more expensive for regular file transformations, especially when simpler serverless options like AWS Glue are available.

CUse Amazon S3 as storage with AWS Glue triggered by S3 events for transformations, and notifyCorrect

AWS Transfer Family integrates natively with Amazon S3. S3 event notifications can trigger serverless AWS Glue jobs for efficient, event-driven transformations, and Amazon SNS provides a managed messaging service, simplifying the architecture and reducing operational overhead.

DUse Amazon EFS with a time-based AWS Glue job every 5 minutes.

Using Amazon EFS is less optimal than S3 for Transfer Family storage, and a time-based AWS Glue job misses the opportunity for event-driven, immediate transformations offered by S3 events.

Concept tested: AWS Transfer Family integration, serverless data transformation (Glue), event-driven architecture (S3 events), and messaging (SNS)

Source: https://docs.aws.amazon.com/transfer/latest/userguide/how-to-s3.html

Community Discussion

No community discussion yet for this question.

Full SAP-C02 Practice