nerdexam
Amazon

MLS-C01 · Question #344

A company is setting up a mechanism for data scientists and engineers from different departments to access an Amazon SageMaker Studio domain. Each department has a unique SageMaker Studio domain…

The correct answer is A. Use the SageMaker CreatePresignedDomainUrl API to generate a presigned URL for each. To provide access to SageMaker Studio domains via a central proxy application using corporate credentials, the proxy should generate temporary, authenticated URLs.

Machine Learning Implementation and Operations

Question

A company is setting up a mechanism for data scientists and engineers from different departments to access an Amazon SageMaker Studio domain. Each department has a unique SageMaker Studio domain. The company wants to build a central proxy application that data scientists and engineers can log in to by using their corporate credentials. The proxy application will authenticate users by using the company's existing Identity provider (IdP). The application will then route users to the appropriate SageMaker Studio domain. The company plans to maintain a table in Amazon DynamoDB that contains SageMaker domains for each department. How should the company meet these requirements?

Options

  • AUse the SageMaker CreatePresignedDomainUrl API to generate a presigned URL for each
  • BUse the SageMaker CreateHumanTaskUi API to generate a UI URL. Pass the URL to the proxy
  • CUse the Amazon SageMaker ListHumanTaskUis API to list all UI URLs. Pass the appropriate
  • DUse the SageMaker CreatePresignedNotebooklnstanceUrl API to generate a presigned URL.

How the community answered

(50 responses)
  • A
    82% (41)
  • B
    2% (1)
  • C
    12% (6)
  • D
    4% (2)

Why each option

To provide access to SageMaker Studio domains via a central proxy application using corporate credentials, the proxy should generate temporary, authenticated URLs.

AUse the SageMaker CreatePresignedDomainUrl API to generate a presigned URL for eachCorrect

The SageMaker CreatePresignedDomainUrl API allows a trusted application, like a central proxy authenticated by an IdP, to generate a temporary, authenticated URL that provides direct, secure access to a specific SageMaker Studio domain for a user without exposing underlying AWS credentials.

BUse the SageMaker CreateHumanTaskUi API to generate a UI URL. Pass the URL to the proxy

The SageMaker CreateHumanTaskUi API is used to create user interfaces for human review tasks, such as those in SageMaker Ground Truth, and is not applicable for granting access to SageMaker Studio domains.

CUse the Amazon SageMaker ListHumanTaskUis API to list all UI URLs. Pass the appropriate

The Amazon SageMaker ListHumanTaskUis API lists human review task UIs and is unrelated to providing access to SageMaker Studio domains.

DUse the SageMaker CreatePresignedNotebooklnstanceUrl API to generate a presigned URL.

The SageMaker CreatePresignedNotebookInstanceUrl API generates URLs for SageMaker Notebook Instances (legacy), not for the newer SageMaker Studio domains mentioned in the question.

Concept tested: SageMaker Studio Access Management

Source: https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreatePresignedDomainUrl.html

Topics

#SageMaker Studio#API Integration#Presigned URLs#Access Control

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full MLS-C01 Practice