Free Amazon Web Services SCS-C02 Practice Exam with Questions & Answers | Set: 7

The most scalable and lowest-latency solution for end-to-end TLS is to configure a Network Load Balancer (NLB) with a TCP listener. This configuration allows TLS traffic to be passed through directly to the containerized applications running on ECS, preserving full encryption between the client and the container without TLS termination at the load balancer.

NLBs are optimized for handling sudden spikes in traffic (volatile traffic patterns), and passing through TLS traffic ensures the encryption is maintained from source to container.

This is a key practice under Infrastructure Security as highlighted in the AWS Certified Security – Specialty content where preserving encryption and handling scale is crucial.

Comprehensive Detailed Explanation with all AWS References

To achieve centralized visibility of security findings from Amazon GuardDuty detectors in multiple AWS accounts under an AWS Organization, the best approach is to integrate GuardDuty withAWS Security Hub.

AWS Security Hub Overview:

Security Hub provides a unified view of security alerts and compliance checks across AWS accounts.

It supports integration with GuardDuty to automatically ingest and display findings in a centralized manner.

because these are the actions that can improve IAM account root user security. IAM account root user is a user that has complete access to all AWS resources and services in an account. IAM account root user security is a set of best practices that help protect the account root user from unauthorized oraccidental use. Deleting the access keys for the account root user in every account can help prevent programmatic access by the account root user, which reduces the risk of compromise or misuse. Enabling MFA on every account root user in all accounts can help add an extra layer of security for console access by requiring a verification code in addition to a password. Creating a custom IAM policy to limit permissions to required actions for the account root user and attaching the policy to the account root user can help enforce the principle of least privilege and restrict the account root user from performing unnecessary or dangerous actions. The other options are either invalid or ineffective for improving IAM account root user security.

To mitigate traffic volume from a specific IP address without entirely blocking it, AWS WAF’s rate-based rules are the appropriate solution. AWS WAF (Web Application Firewall) provides rate-based rules that allow a user to count and limit the rate of requests from individual IP addresses.

A rate-based rule tracks the number of requests that each originating IP makes in a rolling five-minute period. If the number of requests exceeds a specified threshold, WAF applies an action such as block or count.

This makes AWS WAF an ideal tool to throttle traffic rather than block it, which directly meets the use case described.

Reference from AWS Certified Security - Specialty Official Guide:

This capability is part of AWS WAF’s standard feature set, explicitly covered under the topics of Logging and Monitoring and Mitigating DDoS and Abnormal Behavior. Rate-based rules are discussed as a method for limiting the number of incoming requests based on request patterns without denying access outright.

Utilizing AWS Config with a custom AWS Config rule (ec2-managedinstance-applications-required) enables detection of EC2 instances lacking the required software across all accounts in an organization. By creating an Amazon EventBridge rule that triggers on AWS Config events, and configuring it to invoke an AWS Lambda function, automated actions can be taken to ensure compliance. The Lambda function can leverage AWS Systems Manager Run Command to install the necessary software on non-compliant instances. This approach ensures continuous compliance and automated remediation, aligning with best practices for cloud security and management.

Multi-factor authentication can add one more layer of security to your IAM account Even when you go to your Security Credentials dashboard one of the items is to enable MFA on your root account

C:\Users\wk\Desktop\mudassar\Untitled.jpg

Option A is invalid because you need to have a good password policy Option B is invalid because there is no IAM Geo-Lock Option D is invalid because this is not a recommended practices For more information on MFA, please visit the below URL

http://docs.IAM.amazon.com/IAM/latest/UserGuide/id credentials mfa.htmll

The correct answer is: Use MFA on all users and accounts, especially on the root account.

Submit your Feedback/Queries to our Experts

The correct answer is A, C, and E because they provide the most secure and efficient way to implement private connectivity to AWS services. Using interface VPC endpoints for Amazon SQS and gateway VPC endpoints for Amazon S3 allows the application to access these services without using public IP addresses or internet gateways. Modifying the endpoint policies on all VPC endpoints enables the security engineer to specify the SQS and S3 resources that the application uses and restrict access to other resources.

The other options are incorrect because they do not provide private connectivity to AWS services or they introduce unnecessary complexity or cost. Option B is incorrect because AWS Transit Gateway is used to connect multiple VPCs and on-premises networks, not to connect to AWS services. Option D is incorrect because modifying the IAM role applied to the EC2 instances is not sufficient to allow outbound traffic to the interface endpoints. The security group and route table associated with the interface endpoints also need to be configured. Option F is incorrect because AWS Firewall Manager is used to centrally manage firewall rules across multiple accounts and resources, not to connect to AWS services.

A. IAM Access Analyzer helps track and evaluate which resources were accessed and by which principals, aiding in investigating the blast radius.

B. Deactivating the access key is the first and most critical step to immediately prevent further usage of the compromised credentials.

This is consistent with AWS incident response playbooks, which emphasize immediate revocation and impact analysis.