You are a machine learning specialist at a rideshare startup company. Your team supports developers who are using SageMaker notebook instances in a private subnet of your corporate VPC. Your developers have important customer data stored on the SageMaker notebook instance`s EBS volume, and so they wish to take a snapshot of that EBS volume. When your developers attempt to locate the SageMaker notebook EC2 instance and its EBS volume within your corporate VPC, they don’t find them. What is the reason they don’t see the instance or its EBS volume in the corporate VPC?

Answer options:

A.SageMaker notebook instances run on EKS containers running within an AWS service account.
B.SageMaker notebook instances run on EC2 instances running within an AWS service account.
C.SageMaker notebook instances run on the container in the ECS service within your corporate account.
D.SageMaker notebook instances run on the EC2 instances within your corporate account, but they run outside of a VPC.

Correct Answer: B
Option A is incorrect. SageMaker notebook instances run in an AWS service account (not in customer accounts), but they run on EC2 instances, not in EKS containers.
Option B is correct. SageMaker runs its notebook instances on EC2 in an AWS service account, not in customer accounts. Therefore, you can’t access the EC2 instance EBS volumes.
Option C is incorrect. SageMaker notebook instances run in an AWS service account (not in customer accounts), and they run on EC2 instances, not in ECS containers.
Option D is incorrect. SageMaker runs its notebook instances on EC2 in an AWS service account, not in customer accounts.
References:
Please see the Amazon SageMaker developer guide titled Connect SageMaker Studio Notebooks to Resources in a VPC (https://docs.aws.amazon.com/sagemaker/latest/dg/studio-notebooks-and-internet-access.html),
The Amazon EC2 Auto Scaling FAQs page (https://aws.amazon.com/ec2/autoscaling/faqs/),
The AWS Machine Learning blog titled Understanding Amazon SageMaker notebook instance networking configurations and advanced routing options (https://aws.amazon.com/blogs/machine-learning/understanding-amazon-sagemaker-notebook-instance-networking-configurations-and-advanced-routing-options/)