nerdexam
Amazon

MLS-C01 · Question #307

A company plans to build a custom natural language processing (NLP) model to classify and prioritize user feedback. The company hosts the data and all machine learning (ML) infrastructure in the AWS C

The correct answer is A. Create a VPC interface endpoint for the SageMaker notebook in the VPC. Access the notebook. The ML team needs private, non-public internet access to SageMaker notebooks from an on-premises network connected via VPN, with least development effort.

Machine Learning Implementation and Operations

Question

A company plans to build a custom natural language processing (NLP) model to classify and prioritize user feedback. The company hosts the data and all machine learning (ML) infrastructure in the AWS Cloud. The ML team works from the company's office, which has an IPsec VPN connection to one VPC in the AWS Cloud. The company has set both the enableDnsHostnames attribute and the enableDnsSupport attribute of the VPC to true. The company's DNS resolvers point to the VPC DNS. The company does not allow the ML team to access Amazon SageMaker notebooks through connections that use the public internet. The connection must stay within a private network and within the AWS internal network. Which solution will meet these requirements with the LEAST development effort?

Options

  • ACreate a VPC interface endpoint for the SageMaker notebook in the VPC. Access the notebook
  • BCreate a bastion host by using Amazon EC2 in a public subnet within the VPC. Log in to the
  • CCreate a bastion host by using Amazon EC2 in a private subnet within the VPC with a NAT
  • DCreate a NAT gateway in the VPC. Access the SageMaker notebook HTTPS endpoint through a

How the community answered

(36 responses)
  • A
    75% (27)
  • B
    17% (6)
  • C
    3% (1)
  • D
    6% (2)

Why each option

The ML team needs private, non-public internet access to SageMaker notebooks from an on-premises network connected via VPN, with least development effort.

ACreate a VPC interface endpoint for the SageMaker notebook in the VPC. Access the notebookCorrect

Creating a VPC interface endpoint (powered by AWS PrivateLink) for SageMaker Notebooks establishes a private connection directly from the VPC to the SageMaker service. This ensures all traffic remains within the AWS internal network from the VPN-connected on-premises environment, fulfilling the private access requirement with minimal setup effort.

BCreate a bastion host by using Amazon EC2 in a public subnet within the VPC. Log in to the

A bastion host in a public subnet would require traffic to traverse the public internet to reach the bastion host, violating the strict requirement for private network access.

CCreate a bastion host by using Amazon EC2 in a private subnet within the VPC with a NAT

Using a bastion host in a private subnet with a NAT gateway implies public internet access for outbound traffic or a more complex routing setup, adding significant development effort and potentially still routing through public IPs for the SageMaker endpoint if not using PrivateLink.

DCreate a NAT gateway in the VPC. Access the SageMaker notebook HTTPS endpoint through a

A NAT gateway enables instances in private subnets to initiate public internet access; it does not provide private, direct access to SageMaker notebooks from on-premises without routing through the public internet for the SageMaker service endpoint itself.

Concept tested: Private network access to AWS services

Source: https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-interface-vpc-endpoints.html

Topics

#AWS Networking#VPC Interface Endpoint#Amazon SageMaker#Private Connectivity

Community Discussion

No community discussion yet for this question.

Full MLS-C01 Practice