Advanced AWS test (Advanced)

Sample questions

5 sample questions from the Advanced AWS test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. Which of the following statements is correct regarding API Gateway security and AWS WAF integration?

   1. AWS WAF is not compatible with API Gateway.
   2. API Gateway can directly block IP addresses without the use of AWS WAF.
   3. API Gateway can only be secured using AWS Shield.
   4. AWS WAF can be used to protect API Gateway from SQL injection attacks.

   Answer: D. AWS WAF can be used to protect API Gateway from SQL injection attacks.

   AWS WAF (Web Application Firewall) can be integrated with API Gateway to protect against common web exploits such as SQL injection, cross-site scripting (XSS), and other malicious attacks. Other options may refer to features that are not directly supported by API Gateway or are unrelated to security protections.

2. A company is experiencing inefficiencies in their EKS cluster due to high costs and insufficient node capacity during peak times. Upon investigation, it was found that the cluster is not scaling up or down as expected. What is the most likely cause of this issue?

   1. The EKS node group's auto-scaling policy is not configured correctly, and the cooldown period is set too short.
   2. The EKS node group's auto-scaling policy is not configured correctly, and the maximum capacity is set too low to accommodate the workload.
   3. The EKS node group's auto-scaling policy is not configured correctly, and the minimum capacity is set too high to accommodate the workload.
   4. The EKS node group's auto-scaling policy is not configured correctly, and the metrics used for scaling are not properly defined.

   Answer: C. The EKS node group's auto-scaling policy is not configured correctly, and the minimum capacity is set too high to accommodate the workload.

   If the EKS node group's auto-scaling policy is not configured correctly, such as having a minimum capacity that is higher than required, the cluster may not scale down as expected, leading to unnecessary costs and resource inefficiency. This is a common issue when misconfiguring auto-scaling policies. Other options do not directly address the core issue of incorrect auto-scaling policy configuration.

3. How are AWS EKS cluster add-ons typically configured in a realistic project scenario?

   1. EKS add-ons are managed exclusively through the Kubernetes API and require direct access to the EKS control plane.
   2. AWS EKS add-ons are configured using the AWS Management Console, AWS CLI, or AWS CDK, and they are applied at the cluster level through the eksctl tool or the AWS API.
   3. EKS add-ons are applied automatically by the EKS service and cannot be configured manually.
   4. EKS add-ons are configured using Kubernetes manifests and applied directly to the EKS worker nodes.

   Answer: B. AWS EKS add-ons are configured using the AWS Management Console, AWS CLI, or AWS CDK, and they are applied at the cluster level through the eksctl tool or the AWS API.

   AWS EKS add-ons are configured at the cluster level using tools like eksctl, AWS CLI, or AWS CDK. These add-ons are managed by the EKS control plane and are applied during cluster creation or updated afterward. Other options are either incorrect or do not reflect the accurate configuration process for EKS add-ons.

4. A Lambda function using a custom runtime is failing to initialize, and the error logs indicate that the runtime is unable to find the required executable. What is the most likely cause of this issue?

   1. The deployment package does not include the necessary runtime dependencies for the custom Lambda runtime.
   2. The Lambda function's memory allocation is insufficient for the custom runtime to operate.
   3. The IAM role associated with the Lambda function does not have the required permissions for the custom runtime.
   4. The Lambda function timeout is set to less than the time required for the custom runtime to initialize.

   Answer: A. The deployment package does not include the necessary runtime dependencies for the custom Lambda runtime.

   When deploying a custom runtime for AWS Lambda, it is essential to include all necessary dependencies within the deployment package. If the package is missing these dependencies, the Lambda function will fail to start, resulting in errors during execution. This is a common issue when deploying custom runtimes and must be addressed by ensuring the deployment package contains the required runtime files.

5. Which of the following is a cost-optimisation best practice in the Well-Architected Framework when comparing Spot Instances with On-Demand Instances?

   1. Use Reserved Instances for unpredictable, short-term workloads.
   2. Use Spot Instances for batch processing workloads that can tolerate interruptions.
   3. Use On-Demand Instances for long-running, mission-critical applications.
   4. Use Savings Plans for workloads that require guaranteed performance and availability.

   Answer: B. Use Spot Instances for batch processing workloads that can tolerate interruptions.

   Cost optimisation in the Well-Architected Framework involves using cost-effective resources based on workload requirements. Spot Instances are significantly cheaper than On-Demand Instances but can be interrupted. They are ideal for workloads like batch processing that can handle interruptions. On-Demand Instances are more expensive but provide guaranteed availability, making them suitable for critical workloads. Reserved Instances offer long-term savings but require a commitment, while Savings Plans provide flexibility for a broader range of workloads.