Question 610
An MGN migration continuously replicates application server disks to AWS. The team wants to rehearse whether migrated servers boot, attach expected networks and reach dependencies before a production cutover. Which MGN step should be used?
- Execute an MGN cutover launch straight into production before performing any test launch against supported replicated server state.
- Inspect only MGN Replication healthy and declare the operating system, application services and DNS dependencies validated.
- Disable replication synchronization before testing and treat stale blocks as a complete recovery state.
- Launch supported non-disruptive test instances from replicated data and validate application dependencies and cutover runbook.
Explanation
Correct Answer
D:Test launches provide evidence of server operability in AWS while source production continues running.
Incorrect Answers
A:A production cutover cannot substitute for controlled boot, network and dependency evidence gathered during non-disruptive test launches.
B:Replication health measures source block synchronization, not successful boot and application-level functionality on the target.
C:Unverified stale replicated data can cause target correctness failures during cutover.
Question 611
A rehost wave uses AWS MGN and must preserve data created right before the application shutdown window. The proposed cutover simply stops source machines and launches target instances without considering replication backlog. What control is necessary?
- Rely on initial MGN replication completion several days before the source is stopped and avoid measuring later data lag.
- Increase network time-to-live on the source DNS record to guarantee block replication has finished.
- Quiesce application writes, confirm the supported replication lag has reached the intended recovery checkpoint, then perform the cutover.
- Use an MGN test launch as the final production cutover without quiescing source writes or verifying the final data checkpoint.
Explanation
Correct Answer
C:Source quiescence and monitored replication completion reduce data loss during final conversion from source to destination.
Incorrect Answers
A:Initial sync does not guarantee that the last transactions are present without catching up the incremental replication backlog.
B:DNS caching does not synchronize changes between source disks and the MGN replication target.
D:A test instance verifies boot and compatibility, but the final source write set still needs synchronization and controlled cutover.
Question 612
A new AWS enterprise-support customer must move 700 TB of source data from a remote site whose 50-Mbps link cannot meet the shutdown deadline. It can safely copy the data to portable encrypted storage and transport the devices to an accessible AWS Data Transfer Terminal location, but has no pre-existing Snowball Edge account eligibility. Which AWS-supported ingestion approach should it choose in November 2026?
- Order new AWS Snowball Edge devices as a first-time customer in November 2026, ignoring the service availability restrictions.
- Use AWS Data Transfer Terminal with approved customer-owned encrypted devices and a scheduled high-throughput upload session, then validate imported data.
- Select DataSync as the only transfer over the unchanged 50-Mbps remote link and assume its efficient protocol can meet an otherwise impossible 700-TB deadline.
- Request a Direct Connect link from a location without any provisioned circuit and treat the new request as equivalent to transporting prepared encrypted devices now.
Explanation
Correct Answer
B:Data Transfer Terminal provides reservable physical locations for securely uploading data from customer-brought storage at high network throughput, matching the approved logistics and enterprise-support access.
Incorrect Answers
A:AWS Snowball Edge stopped accepting new customers on November 7, 2025; recommending a new Snow order without existing eligibility is not valid for this customer.
C:A managed transfer tool cannot overcome the stated physical last-mile limit; the case supports portable storage transport to an enterprise-only Data Transfer Terminal location.
D:Dedicated connectivity requires provisioning and does not itself solve the deadline at the inaccessible low-bandwidth source location.
Question 613
A company migrated a massive S3 archive using an offline device and kept the source system active during the shipment. On return, source files have changed and the business cannot afford to ship another device. A reliable network is now available for small daily differences. What is the final synchronization plan?
- Restart the complete offline transfer regardless of the small delta and the no-second-shipment constraint.
- Run cutover validation only against the original offline-device shipment manifest and omit source changes made after device dispatch.
- Use a suitable incremental network transfer process such as DataSync for changed files and validate a final delta after a write freeze.
- Replicate every destination object back into the active source just before cutover, overwriting newer source changes with the older snapshot.
Explanation
Correct Answer
C:Bulk offline loading followed by a small incremental delta is appropriate when shipment lag leaves modified source objects.
Incorrect Answers
A:Repeating the whole transfer is unnecessary when only changed objects need reconciliation over the network.
B:A shipment manifest predates ongoing writes, so a final delta reconciliation remains required.
D:Reverse copying stale destination data can lose legitimate updates and does not implement incremental catch-up.
Question 614
An on-premises Windows SMB share contains millions of small files with ACLs and is moving to Amazon FSx for Windows File Server. The organization wants an AWS-managed transfer process that handles file metadata where supported. What should it assess?
- Use AWS Database Migration Service to treat every SMB file as a relational row with CDC.
- Use DataSync with an S3 object destination and assume that object key metadata fully preserves every Windows ACL required by FSx for Windows Server.
- Use AWS MGN to replicate the SMB server operating system into EC2 without transferring its data to the specified FSx share.
- Use AWS DataSync with a supported SMB source and FSx for Windows File Server destination and test ACL/metadata preservation.
Explanation
Correct Answer
D:DataSync supports file transfer to compatible managed storage and can preserve selected metadata under configured conditions.
Incorrect Answers
A:DMS database endpoints do not natively migrate arbitrary SMB filesystem semantics and ACLs.
B:S3 object paths and metadata differ from managed Windows NTFS ACL semantics; the stated destination should be a supported FSx location with appropriate preservation settings.
C:Rehosting the server does not accomplish the required managed file-server destination migration with tested ACL behavior.
Question 615
A business partner transmits purchase orders using the AS2 protocol rather than SFTP. The migration target is a managed AWS service that receives AS2 messages and stores processed data in S3. What service should the architect evaluate?
- Configure AWS Transfer Family AS2 with appropriate trading partner certificates, profiles and S3-backed workflow.
- Provision a Transfer Family SFTP server instead of its supported AS2 endpoint and assume SSH key authentication is accepted as AS2 trading-partner signing.
- Use an EventBridge API Destination HTTP target and assume it replaces every AS2 certificate, signature and message disposition requirement automatically.
- Use a Route 53 private hosted zone as the entire inbound AS2 receiver with no application endpoint.
Explanation
Correct Answer
A:Transfer Family supports AS2 partner exchange when identities and certificates are configured for the selected endpoint.
Incorrect Answers
B:SFTP and AS2 use distinct protocols and certificates/identities; an SFTP endpoint does not implement AS2 interchange.
C:API Destinations can send HTTP requests but do not provide managed AS2 trading-partner signing, encryption and acknowledgment semantics.
D:DNS resolves names but does not receive or validate signed AS2 messages.
Question 616
A plant is migrating an on-premises Windows application that mounts a block disk through iSCSI and requires unchanged block-device semantics for the next six months. The primary dataset can reside in AWS, but frequently read blocks must remain cached locally to accommodate WAN latency. A shared SMB/NFS file namespace is not required. Which Storage Gateway mode is appropriate?
- Use AWS Storage Gateway Volume Gateway in cached-volumes mode, exposing a supported iSCSI target to the on-premises server while keeping primary volume data in AWS.
- Use an S3 File Gateway SMB file share as a drop-in iSCSI block device without changing application storage calls.
- Use only an FSx for Windows SMB share and assert that a network file system is indistinguishable from an iSCSI disk device to the application.
- Use Storage Gateway stored-volume mode even though the plan requires the primary dataset to reside in AWS instead of on-premises disks.
Explanation
Correct Answer
A:Cached Volume Gateway provides iSCSI block volumes with a locally cached hot working set and stores primary data in AWS, matching the legacy block device access model.
Incorrect Answers
B:S3 File Gateway exposes file protocols, not the required block-level iSCSI target semantics for a disk-attached application.
C:An SMB file share is a managed file interface, not an iSCSI block target, and changing the access semantics contradicts the migration constraint.
D:Stored-volume mode retains primary data on the on-premises storage device and snapshots it to AWS, whereas cached-volume mode keeps primary data in AWS with local hot-block caching.
Question 617
A factory must continue running an on-premises application whose Windows server mounts its complete 12-TiB primary working dataset through iSCSI. It has enough locally provisioned disk to store the entire dataset and needs on-site full-speed reads even if the WAN is temporarily unavailable. The cloud requirement is to send durable EBS-compatible recovery snapshots to AWS, NOT to move primary working data into S3. Which Volume Gateway configuration is appropriate?
- Use Volume Gateway stored volumes with primary iSCSI data stored locally and asynchronous EBS snapshots in AWS.
- Use Volume Gateway cached volumes because they always retain the entire primary dataset as a full local copy even when the WAN is disconnected.
- Use S3 File Gateway SMB shares and assume file access automatically appears to this application as the same iSCSI block disk.
- Use FSx for Windows File Server instead of the locally attached iSCSI disk without validating block semantics or WAN disconnection.
Explanation
Correct Answer
A:Stored Volume Gateway keeps the full primary iSCSI volume data on premises while asynchronously protecting it with EBS snapshots, as required by local-capacity and outage constraints.
Incorrect Answers
B:Cached volumes make AWS the primary dataset location and cache frequently accessed blocks locally; they do not guarantee every primary block stays on site during WAN loss.
C:File Gateway serves file shares and cannot transparently replace an unchanged iSCSI block volume for a legacy application.
D:An AWS-managed remote SMB file server does not preserve the stated local iSCSI block path or complete local data availability when the WAN is unavailable.
Question 618
A CRM migration needs to extract customer records from a supported SaaS application into S3 repeatedly for AWS analytics, with connectors and scheduling managed by AWS rather than custom extraction servers. Which service is the direct fit?
- Evaluate Amazon AppFlow with a supported SaaS connector, governed credentials and scheduled flow into S3.
- Deploy a Transfer Family SFTP server on AWS and assume it authenticates directly to the SaaS vendor reporting API and maps records automatically.
- Create an EventBridge rule matching SaaS records even though the third-party provider publishes no supported event integration or data source.
- Create a VPC peering link to the SaaS vendor and infer it performs application data mapping and transfer.
Explanation
Correct Answer
A:AppFlow offers supported managed SaaS-to-AWS data transfers with configurable flows and scheduling.
Incorrect Answers
B:SFTP server hosting handles file transfer sessions, not the SaaS API extraction, schemas and scheduling requested.
C:A rule without a SaaS event source and record-mapping connector cannot pull scheduled data extracts.
D:Network reachability alone does not export records through a supported SaaS application API.
Question 619
A legacy Oracle database contains large objects, and a DMS migration task has been configured in limited LOB mode with a small maximum field size. Users report truncated document columns in the target. Which remediation is appropriate?
- Review DMS LOB migration configuration and select an appropriate supported LOB mode and size strategy, then validate copied rows.
- Increase DMS replication-instance memory and leave a limited LOB mode maximum lower than the actual document value size.
- Switch from limited LOB mode to a schema conversion-only job but stop moving the actual BLOB/CLOB data.
- Ignore migration validation because a successful task status guarantees no large field was truncated.
Explanation
Correct Answer
A:Limited LOB settings can truncate values beyond the configured ceiling; the mode must fit actual large-object requirements.
Incorrect Answers
B:Compute tuning does not remove a configured maximum LOB size that truncates larger values.
C:Schema conversion alone does not transfer oversized application column contents, so a supported LOB transfer strategy remains necessary.
D:Completion does not replace row-level checks or correct an explicit truncation ceiling.
Question 620
A PostgreSQL-to-Aurora PostgreSQL migration uses DMS CDC. After a table schema change, replication events fail because the target schema has not been updated. How should the team handle incompatible DDL during ongoing replication?
- Enable DMS target-table preparation DROP_AND_CREATE for each schema change while active application reads continue, without coordinating target compatibility.
- Coordinate source and target schema changes with tested compatibility, task settings and controlled deployment sequencing.
- Assume DMS CDC always translates and applies every arbitrary source DDL change without validation.
- Increase the DMS target replication-instance class only and ignore the target-column mismatch shown in task errors.
Explanation
Correct Answer
B:Data change replication depends on compatible target tables; uncoordinated schema changes can make incoming events invalid.
Incorrect Answers
A:Dropping/recreating live target tables does not safely translate arbitrary incompatible DDL, and can cause data loss or service interruption.
C:Change data capture does not guarantee complete automated cross-environment schema evolution.
D:More replication CPU cannot repair incompatible target DDL definitions or replay invalid changes automatically.
AWS Certified Solutions Architect - Professional SAP-C02 Practice Tests