MLA-C01 · Question #179
A company runs an Amazon SageMaker AI domain in a public subnet of a newly created VPC. The network is configured properly, and ML engineers can access the SageMaker AI domain. Recently, the company…
The correct answer is B. Create a network ACL inbound rule to deny traffic from the specific IP address. Assign the rule to. Network ACLs are stateless and support explicit deny rules, allowing traffic from a specific source IP address to be blocked at the subnet level. Applying an inbound deny rule on the network ACL associated with the subnet prevents the suspicious traffic from reaching the…
Question
A company runs an Amazon SageMaker AI domain in a public subnet of a newly created VPC. The network is configured properly, and ML engineers can access the SageMaker AI domain. Recently, the company discovered suspicious traffic to the domain from a specific IP address. The company needs to block traffic from the specific IP address. Which update to the network configuration will meet this requirement?
Options
- ACreate a security group inbound rule to deny traffic from the specific IP address. Assign the
- BCreate a network ACL inbound rule to deny traffic from the specific IP address. Assign the rule to
- CCreate a shadow variant for the domain. Configure SageMaker Inference Recommender to send
- DCreate a VPC route table to deny inbound traffic from the specific IP address. Assign the route
How the community answered
(38 responses)- A3% (1)
- B95% (36)
- D3% (1)
Explanation
Network ACLs are stateless and support explicit deny rules, allowing traffic from a specific source IP address to be blocked at the subnet level. Applying an inbound deny rule on the network ACL associated with the subnet prevents the suspicious traffic from reaching the SageMaker AI
Topics
Community Discussion
No community discussion yet for this question.