A company must install a custom script on any newly created Amazon SageMaker notebook instances. Which solution will meet this requirement with the LEAST operational overhead?

Question

Options

• ACreate a lifecycle configuration script to install the custom script when a new SageMaker
• BCreate a custom Amazon Elastic Container Registry (Amazon ECR) image that contains the
• CCreate a custom package index repository. Use AWS CodeArtifact to manage the installation of
• DStore the custom script in Amazon S3. Create an AWS Lambda function to install the custom

• A
  71% (20)
• B
  18% (5)
• C
  7% (2)
• D
  4% (1)

Explanation

Option A is correct because SageMaker lifecycle configuration scripts are a native, built-in feature designed exactly for this use case - they run automatically on instance creation or start, with zero additional infrastructure to manage.

• B (Custom ECR image) requires building, maintaining, and versioning a custom container image, which adds significant ongoing operational overhead every time the base image or script changes.
• C (CodeArtifact package repo) is designed for dependency/package management, not for running arbitrary scripts on instance startup - it's the wrong tool and adds unnecessary complexity.
• D (S3 + Lambda) requires wiring up an event trigger (e.g., EventBridge) to invoke Lambda on notebook creation, maintaining Lambda code, and managing IAM permissions - multiple moving parts where one native feature suffices.

Memory tip: Think "Lifecycle = Least overhead" - whenever an AWS service has a native lifecycle hook (SageMaker, Auto Scaling, Elastic Beanstalk), that hook is almost always the exam's preferred answer over external orchestration with Lambda or custom images.

No community discussion yet for this question.