An ML engineer has an Amazon Comprehend custom model in Account A in the us-east-1 Region. The ML engineer needs to copy the model to Account B in the same Region. Which solution will meet this requir

Question

Options

• AUse Amazon S3 to make a copy of the model. Transfer the copy to Account B.
• BCreate a resource-based IAM policy. Use the Amazon Comprehend ImportModel API operation to
• CUse AWS DataSync to replicate the model from Account A to Account B.
• DCreate an AWS Site-to-Site VPN connection between Account A and Account B to transfer the

• A
  11% (4)
• B
  81% (30)
• C
  5% (2)
• D
  3% (1)

Explanation

Option B is correct because Amazon Comprehend has a built-in ImportModel API designed specifically for cross-account model sharing - you simply attach a resource-based IAM policy to the model in Account A that grants Account B permission, then call ImportModel from Account B to pull it over. This is a native, purpose-built feature requiring minimal code or infrastructure.

Why the distractors fail:

• A (S3 copy): Comprehend doesn't export models as portable artifacts you can download and re-upload; the model is managed internally by the service, so manual S3 copying isn't supported this way.
• C (AWS DataSync): DataSync replicates files between storage systems (S3, EFS, FSx) - it has no awareness of Comprehend model internals and can't transfer a managed ML model between accounts.
• D (Site-to-Site VPN): A VPN connects networks, not AWS accounts/services. It adds massive infrastructure overhead and still wouldn't provide a mechanism to transfer a managed Comprehend model.

Memory tip: When an AWS managed service has a task-specific API verb (like ImportModel, CopySnapshot, or ShareImage), that native API is almost always the least-effort answer for cross-account sharing questions - trust the service's built-in capabilities over DIY infrastructure solutions.

No community discussion yet for this question.