Why is the ML Specialist not seeing the instance visible in the VPC?

A Machine Learning Specialist is using an Amazon SageMaker notebook instance in a private subnet of a corporate VPC. The ML Specialist has important data stored on the Amazon SageMaker notebook instance’s Amazon EBS volume, and needs to take a snapshot of that EBS volume. However, the ML Specialist cannot find the Amazon SageMaker notebook instance’s EBS volume or Amazon EC2 instance within the VPC.

Why is the ML Specialist not seeing the instance visible in the VPC?
A . Amazon SageMaker notebook instances are based on the EC2 instances within the customer account, but they run outside of VPCs.
B . Amazon SageMaker notebook instances are based on the Amazon ECS service within customer accounts.
C . Amazon SageMaker notebook instances are based on EC2 instances running within AWS service accounts.
D . Amazon SageMaker notebook instances are based on AWS ECS instances running within AWS service accounts.

Answer: C

Explanation:

Reference: https://docs.aws.amazon.com/sagemaker/latest/dg/gs-setup-working-env.html

Latest MLS-C01 Dumps Valid Version with 104 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>