Tüm alıştırma soruları

739 soru

Soru 1Soru

A financial services company hosts its customer-facing portal on AWS using a multi-tier architecture. The portal is fronted by an Application Load Balancer (ALB) that routes traffic to Amazon EC2 instances in private subnets. The security team needs to implement a solution to centrally monitor and aggregate security findings across all AWS accounts in the organization, continuously evaluate AWS resource configurations against security best practices (specifically checking for public S3 buckets and overly permissive security groups), and protect the web application from SQL injection attacks and HTTP flood attacks at the application layer. Which combination of AWS services should a solutions architect recommend to meet these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Enable AWS Security Hub across all accounts in the AWS Organization to aggregate findings in a central security administrator account. Enable AWS Config in all accounts to continuously audit security group and Amazon S3 bucket configurations. Deploy AWS WAF on the Application Load Balancer with managed rules to block SQL injection and HTTP flood attacks.

Cevap

The configuration that enables AWS Security Hub for centralized aggregation, AWS Config for configuration compliance auditing, and AWS WAF on the Application Load Balancer for application-layer protection.
The correct architecture uses AWS Security Hub to consolidate security findings across all AWS accounts in the organization, enabling a unified view of the security posture. AWS Config continuously records resource configuration changes and evaluates them against rules (such as checking for public S3 buckets and restricted ports in security groups). To protect the portal against SQL injection and HTTP flood attacks, AWS WAF is deployed on the Application Load Balancer to inspect incoming HTTP/HTTPS traffic at Layer 7.

Adım Adım Çözüm

1
Analyze requirements for application-layer threat protection, continuous resource configuration monitoring, and centralized security aggregation.
Identify that SQL injection and HTTP flood attacks require Layer 7 traffic inspection, configuration auditing requires continuous compliance checking, and centralization requires multi-account findings aggregation.
This establishes the functional boundary for selecting the correct AWS services.
2
Evaluate candidate services for Layer 7 web security.
Determine that AWS WAF is the correct service to block SQL injection and HTTP floods via managed rules, whereas AWS Shield Standard only handles Layer 3 and 4 DDoS protection.
This filters out distractors using Shield Standard for application-layer inspection.
3
Evaluate options for configuration auditing and multi-account compliance monitoring.
Determine that AWS Config audits resource configurations continuously, and AWS Security Hub integrates with AWS Organizations to aggregate these findings into a central administrator account.
This completes the required SAA architecture by leveraging AWS native integration features.

Anahtar Kavram

Centralized security monitoring and application-layer threat detection utilizing AWS Security Hub, AWS Config, and AWS WAF.
Soru 2Soru

A biotechnology company runs computational workflows that simulate molecular interactions. The simulations must be processed in the exact chronological order in which they are submitted to ensure data dependency integrity. Each simulation takes between 11 and 22 hours to execute. The simulation requests are highly irregular, with dozens of submissions occurring simultaneously followed by days of complete inactivity. The database must scale instantly to handle the write throughput when simulations complete, but must not incur compute costs during inactive periods. Which architecture is the most cost-effective and meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Queue the jobs in an Amazon SQS FIFO queue, execute the simulations as Amazon ECS tasks on AWS Fargate, and store the output in an Amazon DynamoDB table configured with on-demand capacity.

Cevap

Queue the jobs in an Amazon SQS FIFO queue, execute the simulations as Amazon ECS tasks on AWS Fargate, and store the output in an Amazon DynamoDB table configured with on-demand capacity.
The correct solution uses an Amazon SQS FIFO queue to enforce strict ordering of the jobs. For the compute layer, Amazon ECS on AWS Fargate is chosen because the simulation runtime of 1 to 2 hours exceeds the 15-minute limitation of AWS Lambda. Fargate is serverless and scales to zero, ensuring zero compute cost when idle. For the database, Amazon DynamoDB in on-demand capacity mode instantly scales to handle completion writes and avoids ongoing idle costs during periods of inactivity.

Adım Adım Çözüm

1
Analyze the ordering requirement.
Since the simulation jobs must be processed in the exact chronological order of submission, an Amazon SQS FIFO (First-In-First-Out) queue is required, eliminating standard SQS options.
Amazon SQS standard queues do not guarantee message ordering, whereas SQS FIFO queues ensure strict order-of-arrival processing.
2
Analyze the compute runtime and serverless scaling requirement.
AWS Fargate must be used instead of AWS Lambda.
Each simulation runs for 1 to 2 hours, which exceeds the 15-minute execution limit of AWS Lambda. Running containerized tasks on AWS Fargate allows execution times up to several days while remaining serverless and scaling to zero when idle.
3
Analyze the database capacity mode for the irregular workload.
Amazon DynamoDB must be configured with on-demand capacity mode.
On-demand capacity mode dynamically scales to handle instant write spikes and does not charge for idle capacity during inactive periods, whereas provisioned capacity mode would incur ongoing costs for idle resources.

Anahtar Kavram

Selecting cost-effective serverless compute and database capacity modes for irregular, long-running tasks requiring ordered processing.
Soru 3Soru

A financial services firm hosts a customer-facing web application on AWS behind an Application Load Balancer (ALB). The security team needs to implement a solution to monitor for and automatically block SQL injection attacks at the application layer. Additionally, they must ensure that all administrative and management API actions across the entire AWS account are recorded and audited for regulatory compliance. Which combination of actions should a solutions architect recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy AWS WAF on the Application Load Balancer with a rule group to detect and block SQL injection attacks, and configure AWS CloudTrail with a multi-region trail to log all API activity to a secure Amazon S3 bucket.

Cevap

Deploy AWS WAF on the Application Load Balancer with a rule group to detect and block SQL injection attacks, and configure AWS CloudTrail with a multi-region trail to log all API activity to a secure Amazon S3 bucket.
The correct answer combines AWS WAF, which inspects HTTP/S traffic at Layer 7 to block SQL injection attacks, with AWS CloudTrail, which logs API and management console activities for compliant security monitoring.

Adım Adım Çözüm

1
Determine the correct service to monitor and mitigate Layer 7 application exploits.
AWS WAF is selected because it is designed to analyze HTTP payloads and block SQL injection attacks at the Application Load Balancer.
Other services like AWS Shield Standard or Network ACLs operate at network layers and cannot perform application payload inspection.
2
Select the appropriate compliance logging mechanism for AWS account administrative API activity.
AWS CloudTrail is chosen to record API calls and management events.
CloudTrail provides standard auditing logs for all management console, CLI, and SDK operations.
3
Combine into a secure, Well-Architected solution.
WAF is attached to the ALB, and a multi-region CloudTrail logs all API activity to a secure Amazon S3 bucket.
This guarantees real-time mitigation of application exploits and audit records stored securely for compliance.

Anahtar Kavram

Application-layer threat detection and compliance logging on AWS
Tahmini Süre:2m 0s
Soru 4Soru

A startup is launching a mobile game that stores user profile data. The game's traffic is highly unpredictable and spiky, with writes to the database increasing from 100 writes per second to over 12,000 writes per second within minutes when popular influencers stream the game. Outside of these events, traffic is minimal. The database must be highly available and scale automatically to handle these sudden spikes. Which database configuration meets these requirements most cost-effectively?

Cevabı ve açıklamayı göster

Cevap: Amazon DynamoDB configured in on-demand capacity mode

Cevap

Amazon DynamoDB configured in on-demand capacity mode
The correct answer is the option proposing Amazon DynamoDB in on-demand capacity mode. For highly unpredictable workloads with sudden, massive spikes followed by periods of inactivity, DynamoDB on-demand capacity mode is the most cost-effective choice. It scales automatically and instantly to accommodate write spikes up to 12,000 writes per second and incurs no charges when the database is idle, charging only for actual read and write requests.

Adım Adım Çözüm

1
Analyze workload characteristics
The workload has extreme write spikes (from 100 to 12,000 writes/sec) that occur rapidly (within minutes) and are highly unpredictable, with long periods of idle time.
Understanding the traffic pattern is critical to choosing the correct database capacity model.
2
Evaluate DynamoDB on-demand capacity mode against the workload profile
On-demand capacity mode instantly scales to accommodate sudden, unpredictable spikes in traffic and charges only for the actual requests consumed, making it highly cost-optimized for this pattern.
This mode avoids paying for idle resources while ensuring the database does not throttle during sudden spikes.
3
Compare with alternative configurations
Provisioned capacity with Auto Scaling cannot scale up quickly enough to handle sudden spikes from 100 to 12,000 writes per second, leading to database throttling. Statically provisioning for peak load is extremely expensive and wasteful during idle periods. Single-AZ RDS with a Read Replica is not a valid automated high availability option and cannot scale writes dynamically.
Confirming why the other options fail to meet the cost and performance requirements.

Anahtar Kavram

Selecting the optimal database capacity mode (on-demand vs. provisioned) based on workload predictability and scaling velocity to minimize cost while maintaining performance.
Tahmini Süre:1m 30s
Soru 5Soru

A company has an on-premises Active Directory and is migrating its web application to AWS. The application runs on Amazon EC2 instances. The solutions architect must ensure that:
1. Corporate employees can access the AWS Management Console using their existing credentials, without creating individual IAM users.
2. The EC2 instances can securely access a private Amazon S3 bucket without using long-term credentials.
3. Administrative operations in the AWS account must be restricted to standard IAM administrative roles, ensuring the root user is not used for daily activities.

Which combination of steps should the solutions architect implement to meet these security requirements?

Cevabı ve açıklamayı göster

Cevap: Configure AWS IAM Identity Center to federate the on-premises Active Directory. Attach an IAM role with an instance profile to the EC2 instances to grant temporary permissions to access the S3 bucket. Create a dedicated IAM role with administrative policies for daily cloud administration instead of using the AWS account root user.

Cevap

Configure AWS IAM Identity Center to federate the Active Directory, use an IAM role with an instance profile for EC2 S3 access, and use a dedicated administrative IAM role for daily tasks instead of the root user.
The correct solution uses AWS IAM Identity Center to federate Active Directory identities, which fulfills the requirement of single sign-on without manual IAM user overhead. It employs an IAM role with an instance profile to supply temporary credentials to EC2 instances, adhering to credential management best practices. Finally, it uses a dedicated administrative IAM role for daily tasks rather than exposing the root user account.

Adım Adım Çözüm

1
Configure AWS IAM Identity Center to federate Active Directory.
Employees can log in with corporate credentials without creating duplicate IAM users in AWS.
Allows centralized identity management and avoids the creation of static IAM users.
2
Assign an IAM role with an instance profile to the EC2 instances.
The application automatically obtains temporary AWS security credentials to access S3.
Eliminates the risk of hardcoded, static credentials on the EC2 instances.
3
Deploy a dedicated IAM role for administrator duties.
Administrative operations are performed securely without using the AWS account root user.
Protects the root account by restricting daily administrative actions to standard IAM roles.

Anahtar Kavram

Identity Federation, IAM Roles, and Least Privilege Account Management
Soru 6Soru

An enterprise is migrating its multi-account environment to AWS Organizations. The security team needs to enforce compliance by preventing any member account under the `Prod-Workloads` OU from deleting or modifying administrative IAM roles prefixed with `SecurityGov-`. Additionally, the enterprise requires centralized access management integrated with their Microsoft Entra ID identity provider. The solution must ensure that administrative tasks in member accounts do not require local IAM user credentials. Which strategy should a Solutions Architect implement to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure federated access using AWS IAM Identity Center integrated with Microsoft Entra ID. Attach an SCP to the `Prod-Workloads` OU that denies `iam:DeleteRole`, `iam:PutRolePolicy`, and `iam:AttachRolePolicy` actions for any resource prefixed with `SecurityGov-`, except when the principal is the IAM Identity Center administrative role.

Cevap

Configure federated access using AWS IAM Identity Center integrated with Microsoft Entra ID, and attach an SCP to the target OU denying modification of security roles with an exception for the admin role.
The correct strategy integrates Microsoft Entra ID with AWS IAM Identity Center for centralized access without requiring local IAM users. Using an SCP applied to the `Prod-Workloads` OU enforces the security guardrails on member accounts while exempting the admin role to allow legitimate updates to the security roles.

Adım Adım Çözüm

1
Analyze identity requirements
Determine that centralized federation using AWS IAM Identity Center is required to integrate with Microsoft Entra ID and avoid local credentials.
This simplifies credential management and aligns with AWS best practices for identity federation.
2
Analyze guardrail requirements
Establish that an SCP (Service Control Policy) attached to the `Prod-Workloads` OU is the correct mechanism to restrict role modification globally across the target member accounts.
SCPs enforce controls across accounts in an OU regardless of local administrator permissions.
3
Define SCP exceptions
Write the SCP to deny IAM modifications on the `SecurityGov-` role prefix, adding a condition that exempts the IAM Identity Center administrative role to allow legitimate changes.
A strict deny would block all users, including the central administrators, from managing the resources.

Anahtar Kavram

Centralized identity federation and multi-account guardrail enforcement using Service Control Policies (SCPs).
Soru 7Soru

A digital publishing company serves personalized web content to a global audience. The content is hosted on origin servers in an on-premises data center, which is connected to AWS via an AWS Direct Connect connection. During major news events, the platform experiences sudden HTTP flood attacks (Layer 7) that exhaust the bandwidth on the Direct Connect connection, causing severe outages for legitimate users. The company needs to implement a solution to block these attacks at the AWS network edge before they reach the Direct Connect connection and the on-premises infrastructure. Which solution will meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Create an Amazon CloudFront distribution with the on-premises origin servers configured as the origin. Associate an AWS WAF web ACL with the CloudFront distribution, configure rate-based rules, and enable AWS Shield Advanced on the CloudFront distribution.

Cevap

Create an Amazon CloudFront distribution with the on-premises origin servers configured as the origin, associate an AWS WAF web ACL with rate-based rules, and enable AWS Shield Advanced.
The correct solution uses Amazon CloudFront to intercept traffic at the AWS edge, which prevents malicious HTTP requests from traversing the Direct Connect link and exhausting the bandwidth of the on-premises origin. Associating an AWS WAF web ACL with rate-based rules blocks the Layer 7 HTTP flood attacks, and enabling AWS Shield Advanced on the CloudFront distribution provides advanced monitoring and automated Layer 7 mitigation.

Adım Adım Çözüm

1
Analyze the entry point of the network traffic and identify where the bottleneck occurs.
The traffic traverses a Direct Connect connection to the on-premises origin, meaning any DDoS mitigation must happen at the AWS edge before entering the Direct Connect path.
This determines that resources inside the VPC or on-premises cannot protect the Direct Connect link bandwidth.
2
Select an AWS service that can act as a global entry point at the edge and integrate with layer 7 protection.
Amazon CloudFront can cache content, serve as the public entry point, and support AWS WAF and AWS Shield Advanced.
CloudFront routes traffic through the global AWS edge network, isolating the origin from direct internet exposure.
3
Apply Layer 7 mitigation to block HTTP flood attacks.
AWS WAF with rate-based rules blocks anomalous IP request rates, and AWS Shield Advanced provides automated Layer 7 protection.
Layer 7 attacks mimic real traffic, requiring application-layer analysis and rate-limiting to mitigate without blocking legitimate traffic.

Anahtar Kavram

Edge protection and DDoS mitigation for hybrid architectures
Tahmini Süre:2m 30s
Soru 8Soru

An online retail application hosted on AWS Lambda requires access to an external payment gateway API key that must be rotated every 30 days. The application also requires access to several non-sensitive configuration settings, including timeout values and API endpoints. The architecture must minimize cost while ensuring that the sensitive API key is encrypted at rest and rotated automatically without manual intervention. Which parameter management strategy should a solutions architect implement to meet these requirements with the lowest operational overhead?

Cevabı ve açıklamayı göster

Cevap: Store the non-sensitive parameters as Standard parameters in AWS Systems Manager Parameter Store. Store the payment gateway API key in AWS Secrets Manager, and configure automatic rotation using an AWS Lambda function.

Cevap

Store the non-sensitive parameters as Standard parameters in AWS Systems Manager Parameter Store, store the payment gateway API key in AWS Secrets Manager, and configure automatic rotation using an AWS Lambda function.
The correct solution uses AWS Systems Manager Parameter Store for non-sensitive parameters, which is cost-effective, and AWS Secrets Manager for the sensitive API key. Secrets Manager supports automatic rotation natively through integration with AWS Lambda, ensuring that the 30-day rotation requirement is met with minimal custom development or operational maintenance.

Adım Adım Çözüm

1
Identify parameter types and security requirements.
Non-sensitive settings (timeout, endpoints) do not require encryption or rotation. The payment gateway API key requires encryption at rest and automatic rotation every 30 days.
This determines the appropriate service for each parameter class to optimize cost and security.
2
Select the parameter storage service based on cost and capability constraints.
Use Systems Manager Parameter Store Standard parameters for non-sensitive settings to avoid cost. Use AWS Secrets Manager for the API key to utilize its native rotation integration.
Parameter Store standard parameters are free, whereas Secrets Manager charges per secret but provides built-in rotation management.
3
Configure automatic rotation for the API key.
Configure AWS Secrets Manager to rotate the API key every 30 days using a rotation AWS Lambda function.
This automates the rotation lifecycle of the external API key, meeting the security mandate with the least operational overhead.

Anahtar Kavram

Secrets Manager vs Parameter Store Trade-offs
Tahmini Süre:1m 30s
Soru 9Soru

An enterprise application hosted on Amazon ECS tasks in a private VPC must connect to a legacy PostgreSQL database hosted on-premises via an AWS Direct Connect connection. The database credentials must be rotated every 30 days to comply with security regulations. The rotation process must be automated, secure at rest, and must not require changes to the application deployment pipeline. Which database credential management solution meets these security requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Store the database credentials in AWS Secrets Manager. Configure a 30-day rotation schedule for the secret and deploy a custom AWS Lambda function within the VPC to update the credentials on both the PostgreSQL database and the Secrets Manager secret.

Cevap

Store the database credentials in AWS Secrets Manager, configuring a 30-day rotation schedule along with a custom AWS Lambda function in the VPC to update the credentials in both the database and the secret.
The correct solution uses AWS Secrets Manager, which natively orchestrates credential rotation. Because the target PostgreSQL database is legacy and on-premises, a custom Lambda function running in the private VPC is required to bridge the connectivity over AWS Direct Connect and safely update both the database password and the secrets store.

Adım Adım Çözüm

1
Select a secrets management service that supports secure storage and automated rotation.
AWS Secrets Manager is chosen over Systems Manager Parameter Store because Secrets Manager has built-in integration for automated rotation schedules.
Parameter Store lacks native credential rotation orchestration and requires building custom schedulers and notification flows.
2
Ensure network connectivity for the rotation mechanism.
The Lambda rotation function must be associated with the VPC to route traffic over the AWS Direct Connect connection to the on-premises database.
Since the database is private on-premises, a Lambda function running outside the VPC cannot resolve or connect to the database endpoints.
3
Configure rotation mechanics using the rotation Lambda function.
The Lambda function updates the credential on the PostgreSQL database first, verifies connectivity, and then calls the Secrets Manager API to update the secret value.
This guarantees that the credential in the secret manager is always synchronized with the database, avoiding service disruption.

Anahtar Kavram

Secrets Manager vs Parameter Store Rotation and Encryption Mechanics
Soru 10Soru

A company is using AWS Organizations to manage a multi-account environment. The security team wants to implement a centralized identity management solution that allows corporate employees to authenticate using their existing external Identity Provider (IdP) credentials and access resources across multiple AWS accounts. Additionally, the security team needs to prevent individual member accounts from disabling AWS CloudTrail logging. Which solution meets these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Configure AWS IAM Identity Center to federate with the external IdP. Assign permission sets to users and groups for AWS Organizations member accounts. Apply a Service Control Policy (SCP) at the root level of the organization that denies the cloudtrail:StopLogging and cloudtrail:DeleteTrail actions on all member Organizational Units (OUs).

Cevap

Configure AWS IAM Identity Center to federate with the external Identity Provider (IdP), assign permission sets to users and groups for AWS Organizations member accounts, and apply a Service Control Policy (SCP) at the root level of the organization to deny cloudtrail:StopLogging and cloudtrail:DeleteTrail actions on all member Organizational Units (OUs).
The correct solution uses AWS IAM Identity Center to establish federation with the external Identity Provider, enabling centralized authentication without creating individual IAM users. By applying a Service Control Policy at the Organization root level, the policy is inherited by all member accounts and organizational units, preventing administrators in member accounts from stopping or deleting AWS CloudTrail.

Adım Adım Çözüm

1
Configure AWS IAM Identity Center to federate with the external Identity Provider (IdP).
Establishes a single sign-on (SSO) gateway allowing enterprise users to access AWS accounts using their existing corporate credentials without local IAM user provisioning.
Reduces operational overhead and centralizes identity management by delegating authentication to the external IdP.
2
Create permission sets and assign them to users and groups across the organization accounts.
Users and groups receive permissions defined by the permission sets in specific AWS accounts.
Allows fine-grained access control across multiple accounts in AWS Organizations.
3
Create and attach a Service Control Policy (SCP) to the organization's root or member OUs that denies CloudTrail deletion and stop logging actions.
Ensures all member accounts inherit the policy, prohibiting users (including account administrators) from stopping or deleting trails.
Enforces governance and compliance controls uniformly across all member accounts in a multi-account organization.

Anahtar Kavram

Centralized federation and organization-wide governance policies using AWS IAM Identity Center and Service Control Policies (SCPs).
Tahmini Süre:2m 0s
Soru 11Soru

A ride-sharing platform is designing an event-driven system to process ride status updates (such as requested, accepted, driver_arrived, and ride_ended) sent from driver mobile applications. To maintain a correct trip history, updates for each specific ride must be processed in the exact sequence they are generated. The platform must handle sudden spikes in traffic during peak hours without losing messages, and the upstream ingestion layer must be decoupled from the downstream processing application. Which solution meets these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Publish the updates to an Amazon SNS FIFO topic. Subscribe an Amazon SQS FIFO queue to the topic, and configure the downstream application to process messages from the queue using the ride ID as the message group ID.

Cevap

Publish the updates to an Amazon SNS FIFO topic. Subscribe an Amazon SQS FIFO queue to the topic, and configure the downstream application to process messages from the queue using the ride ID as the message group ID.
The correct solution uses an Amazon SNS FIFO topic subscribed to by an Amazon SQS FIFO queue. SNS FIFO and SQS FIFO queues guarantee first-in, first-out (FIFO) delivery within a message group. By setting the ride ID as the message group ID, the platform ensures that updates for any single ride are processed in the order they were sent. This serverless solution handles scaling and message buffering automatically, minimizing operational overhead.

Adım Adım Çözüm

1
Analyze the requirements for message ordering and decoupling.
Identified that the solution must guarantee strict ordering of messages per ride ID (sequence of status updates) and decouple upstream mobile apps from downstream processing.
This helps narrow down the choices to AWS messaging services that support FIFO (First-In-First-Out) capabilities.
2
Evaluate the capabilities of Amazon SNS and SQS for ordering.
Standard SNS and SQS queues do not guarantee ordering, whereas SNS FIFO and SQS FIFO queues guarantee strict ordering of messages within the same message group.
The ride ID must be used as the message group ID to ensure that messages belonging to the same ride are processed in sequence.
3
Select the option with the least operational overhead.
The serverless combination of SNS FIFO and SQS FIFO requires no infrastructure management and satisfies all decoupling and ordering constraints.
Custom solutions using ElastiCache or other databases require provisioning and management of compute resources, resulting in higher operational overhead.

Anahtar Kavram

Decoupling event-driven architectures requiring strict message ordering using SNS/SQS FIFO.
Soru 12Soru

An organization operates a multi-account AWS environment managed under AWS Organizations. An application running on Amazon EC2 instances in a production member account must securely access and decrypt highly confidential financial data stored in an Amazon S3 bucket within a shared services account. The S3 bucket is encrypted with an AWS KMS customer managed key located in the shared services account. The solution must also retrieve database credentials that require rotation every 3030 days.

Which design should a solutions architect implement to meet these security requirements?

Cevabı ve açıklamayı göster

Cevap: Attach an IAM instance profile to the EC2 instances that references an IAM role. Configure the KMS key policy and the S3 bucket policy in the shared services account to grant permissions to the EC2 role. Store the database credentials in AWS Secrets Manager and enable automatic rotation every 3030 days using an AWS Lambda function.

Cevap

Attach an IAM instance profile to the EC2 instances that references an IAM role, configure cross-account permissions in the shared services account's S3 bucket policy and KMS key policy to trust the role, and store and automatically rotate the credentials in AWS Secrets Manager using a Lambda function.
The correct solution uses an IAM instance profile to assign temporary credentials to the EC2 instances. For cross-account access to S3 and KMS in the shared services account, both the S3 bucket policy and the KMS key policy must trust the EC2 role from the production account. Storing and rotating database credentials every 3030 days is a native capability of AWS Secrets Manager using AWS Lambda, representing the most secure and low-overhead solution.

Adım Adım Çözüm

1
Configure the identity foundation for the EC2 instances using temporary credentials.
Create an IAM role and associate it with an IAM instance profile attached to the EC2 instances, eliminating the need for hardcoded credentials.
This follows the security principle of least privilege and avoids storing long-term credentials on EC2 instances.
2
Establish trust and permissions across AWS accounts.
Update the S3 bucket policy and KMS key policy in the shared services account to grant the required permissions (such as s3:GetObject and kms:Decrypt) to the ARN of the IAM role in the production account.
For cross-account access, both the IAM policy in the source account and the resource policies in the target account must allow the operations.
3
Securely store and automate rotation of the database credentials.
Store the database credentials in AWS Secrets Manager, and configure the built-in rotation mechanism with an AWS Lambda function set to trigger every 3030 days.
AWS Secrets Manager is designed to manage database secrets securely and provides out-of-the-box integration with AWS Lambda to rotate credentials automatically.

Anahtar Kavram

Cross-account resource access using IAM roles combined with secure secrets management and rotation.
Tahmini Süre:2m 30s
Soru 13Soru

An organization hosts a legacy payroll application on Amazon EC2 instances managed by an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The payroll application runs on port 8088. The target group is configured to route HTTP traffic to the EC2 instances on port 8088. The EC2 instances are in a security group that allows inbound traffic on port 8088 from the ALB's security group. However, the ALB marks all registered EC2 instances as unhealthy. A solutions architect discovers that the target group's health checks are configured to use HTTP on port 80. How should the solutions architect resolve this issue and restore the system to a healthy state?

Cevabı ve açıklamayı göster

Cevap: Modify the target group's health check settings to use port 8088 or set the health check port to traffic-port.

Cevap

Modify the target group's health check settings to use port 8088 or set the health check port to traffic-port.
The correct option is to modify the target group's health check settings to use port 8088 or 'traffic-port'. By default, the ALB target group health check uses the port configured for traffic routing ('traffic-port') unless overridden. If it was overridden to port 80, the health check requests will be sent to port 80 on the EC2 instances. Since the payroll application is listening on port 8088 and no service is listening on port 80, the health checks will fail. Correcting the health check port resolves this mismatch.

Adım Adım Çözüm

1
Analyze the application listening port and the target group health check configuration.
The application is listening on port 8088, but health checks are being sent to port 80.
Identify the mismatch between where the service is active and where the load balancer is querying for health status.
2
Determine the impact of the configuration mismatch.
Since no process on the EC2 instances is listening on port 80, connection attempts by the ALB fail, and instances are marked unhealthy.
Explain why the instances are failing the health checks despite having security group rules permitting traffic on port 8088.
3
Align the health check port with the application port.
Change the health check port configuration to port 8088 or specify 'traffic-port' to dynamically match the target group's routing port.
Ensures the health check queries the port where the payload application is running, allowing successful health status updates.

Anahtar Kavram

ELB Target Group Health Check Port Configuration
Tahmini Süre:1m 30s
Soru 14Soru

A data processing application is deployed on Amazon EC2 instances in a private subnet (Subnet A: 10.0.2.0/2410.0.2.0/24). The application must initiate outbound database queries to an Amazon RDS PostgreSQL DB instance in another private subnet (Subnet B: 10.0.3.0/2410.0.3.0/24) on port 54325432. The application must also download external software updates over HTTPS (port 443443) through a NAT Gateway located in a public subnet (Subnet C: 10.0.1.0/2410.0.1.0/24). Custom Network Access Control Lists (NACLs) are used to secure the subnets. Which configuration of NACL rules for Subnet A will allow the required traffic while following the principle of least privilege?

Cevabı ve açıklamayı göster

Cevap: Inbound: Allow traffic from Source 0.0.0.0/00.0.0.0/0 on Port Range 1024655351024-65535. Outbound: Allow traffic to Destination 10.0.3.0/2410.0.3.0/24 on Port 54325432 and to Destination 0.0.0.0/00.0.0.0/0 on Port 443443.

Cevap

Inbound: Allow traffic from Source 0.0.0.0/00.0.0.0/0 on Port Range 1024655351024-65535. Outbound: Allow traffic to Destination 10.0.3.0/2410.0.3.0/24 on Port 54325432 and to Destination 0.0.0.0/00.0.0.0/0 on Port 443443.
Network Access Control Lists (NACLs) are stateless network filters applied at the subnet boundary. Because they are stateless, both outbound request traffic and inbound response traffic must be explicitly permitted. When the EC2 instances in Subnet A initiate outbound connections to the database (port 54325432) and the external update repository (port 443443), they select a random source port from the ephemeral port range (1024655351024-65535). The returning packets from these services will target these ephemeral ports on the EC2 instances. Therefore, the inbound NACL rules must allow return traffic from any source (0.0.0.0/00.0.0.0/0) targeting the ephemeral port range (1024655351024-65535).

Adım Adım Çözüm

1
Analyze the traffic requirements and directions for the EC2 instances in Subnet A.
Outbound traffic consists of database queries to Subnet B (10.0.3.0/2410.0.3.0/24) on port 54325432 and HTTPS requests to the internet (via NAT Gateway) on port 443443.
Understanding the traffic destination and ports determines the outbound NACL rules.
2
Determine how the stateless nature of NACLs impacts return traffic.
Return traffic from both the database and the internet will target the ephemeral port range (1024655351024-65535) on the EC2 instances in Subnet A.
NACLs are stateless, so return traffic must be explicitly allowed by inbound rules.
3
Select the minimum required NACL rules to allow both outbound and inbound traffic.
Outbound rules must permit port 54325432 to 10.0.3.0/2410.0.3.0/24 and port 443443 to 0.0.0.0/00.0.0.0/0. Inbound rules must permit port range 1024655351024-65535 from 0.0.0.0/00.0.0.0/0.
This configuration allows initiating requests and receiving responses while keeping other ports blocked.

Anahtar Kavram

Stateless behavior of Network Access Control Lists (NACLs) and ephemeral port configurations
Tahmini Süre:2m 0s
Soru 15Soru

A company is designing the access control mechanism for its development team. The developers need to access AWS resources to deploy applications. The security team mandates that developers must use their existing corporate directory credentials to log in, and no long-term AWS credentials should be stored on developer machines. Additionally, sensitive database credentials used by the applications must be stored securely and rotated automatically every 30 days. Which combination of AWS services and configurations should a solutions architect recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure AWS IAM Identity Center to federate with the corporate directory, allowing developers to assume short-term IAM roles. Use AWS Secrets Manager to store the database credentials and configure automatic rotation.

Cevap

Configure AWS IAM Identity Center to federate with the corporate directory, allowing developers to assume short-term IAM roles. Use AWS Secrets Manager to store the database credentials and configure automatic rotation.
The correct configuration uses AWS IAM Identity Center to federate with the corporate directory, allowing developers to authenticate with their existing credentials and assume short-term roles instead of using long-term credentials. Additionally, using AWS Secrets Manager to store and automatically rotate the database credentials satisfies the security policy for encrypting and rotating sensitive data.

Adım Adım Çözüm

1
Address the federated access requirement by configuring AWS IAM Identity Center to integrate with the corporate directory, which enables single sign-on using corporate credentials without creating permanent IAM users.
Developers can authenticate using their existing corporate credentials and obtain short-term credentials via IAM roles.
This removes the need to store long-term access keys on developer machines, meeting the primary security constraint.
2
Address the sensitive database credentials requirement by storing them in AWS Secrets Manager.
Credentials are encrypted at rest and can be retrieved programmatically.
Secrets Manager provides native support for encrypting secrets and automatically rotating them using built-in integration with databases.

Anahtar Kavram

AWS identity federation using IAM Identity Center combined with secure secrets management using AWS Secrets Manager.
Soru 16Soru

A logistics company hosts a shipment tracking portal on AWS. The application runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The portal has recently experienced HTTP flood attacks targeting the search endpoint, which overloads the ALB and causes application downtime. A solutions architect must design a secure architecture that mitigates these Layer 7 DDoS attacks at the AWS edge network before they reach the ALB.

Which solution meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon CloudFront distribution in front of the ALB. Create an AWS WAF web ACL with a rate-based rule and associate it with the CloudFront distribution.

Cevap

Deploy an Amazon CloudFront distribution in front of the ALB. Create an AWS WAF web ACL with a rate-based rule and associate it with the CloudFront distribution.
The correct option is to deploy Amazon CloudFront in front of the ALB and associate it with an AWS WAF web ACL configured with a rate-based rule. AWS WAF rate-based rules track the number of requests from each originating IP address and block requests that exceed a defined threshold. Deploying this at the CloudFront distribution leverages the AWS edge network, stopping the DDoS traffic before it reaches the backend infrastructure.

Adım Adım Çözüm

1
Shift the application entry point to the AWS edge network by deploying Amazon CloudFront.
Inbound user traffic is routed through AWS edge locations rather than directly hitting the ALB.
This establishes an edge protection layer and absorbs traffic closer to the users.
2
Create an AWS WAF web ACL with a rate-based rule.
A security rule is established that tracks the rate of requests from individual IP addresses over a rolling 5-minute period.
Rate-limiting is the standard mechanism to mitigate HTTP flood attacks at the application layer.
3
Associate the AWS WAF web ACL with the CloudFront distribution.
Excessive requests are blocked at the edge network, ensuring only legitimate traffic is forwarded to the ALB.
This prevents malicious Layer 7 traffic from consuming ALB resources or reaching the EC2 origin servers.

Anahtar Kavram

Mitigating Layer 7 DDoS attacks at the edge using Amazon CloudFront and AWS WAF rate-based rules.
Soru 17Soru

A retail technology startup has a multi-account AWS environment managed under AWS Organizations. The startup uses Okta as its central Identity Provider (IdP) for employee authentication. The security team wants to grant developers single sign-on (SSO) access to their respective AWS accounts. The solution must ensure that user access is automatically provisioned and deprovisioned when users are added or removed in Okta, while minimizing operational complexity and eliminating the use of long-term credentials. Which solution meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Enable AWS IAM Identity Center, configure Okta as an external identity provider (IdP) using SAML 2.0, and configure automatic provisioning using the System for Cross-domain Identity Management (SCIM) v2.0 protocol.

Cevap

Enable AWS IAM Identity Center, configure Okta as an external identity provider (IdP) using SAML 2.0, and configure automatic provisioning using the System for Cross-domain Identity Management (SCIM) v2.0 protocol.
The correct solution uses AWS IAM Identity Center to federate Okta as an external Identity Provider (IdP) via SAML 2.0. This allows users to authenticate using their corporate credentials. Enabling System for Cross-domain Identity Management (SCIM) v2.0 ensures that user provisioning and deprovisioning are handled automatically when accounts are modified in Okta, meeting the requirement to minimize operational complexity without using long-term credentials.

Adım Adım Çözüm

1
Select AWS IAM Identity Center as the central service for managing SSO access across multiple accounts in AWS Organizations.
Establishes a centralized identity hub that eliminates the need to configure IAM resources individually in every account.
Reduces operational complexity and simplifies management.
2
Configure SAML 2.0 federation between AWS IAM Identity Center and Okta.
Enables single sign-on using Okta as the authoritative identity provider.
Allows developers to authenticate with their existing corporate credentials without using long-term AWS IAM credentials.
3
Enable and configure automatic provisioning using the SCIM v2.0 protocol in AWS IAM Identity Center and Okta.
Automatically synchronizes user accounts, group memberships, and status updates.
Ensures that when a user is added to or removed from Okta, their access in AWS is immediately granted or revoked, maintaining security and compliance.

Anahtar Kavram

Centralized Identity Federation with Automatic SCIM Provisioning
Tahmini Süre:1m 30s
Soru 18Soru

A clinical diagnostic laboratory is building an event-driven system to process patient test results generated by multiple automated analyzers. The results for each patient must be processed in the exact sequence they are completed to prevent older results from overwriting newer ones due to network latency. Results for different patients can be processed concurrently. The system must scale automatically to handle sudden increases in test volumes during peak hours.

Which solution meets these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Create an Amazon SQS FIFO queue and configure an AWS Lambda function as the consumer. Send the events to the queue using the patient ID as the message group ID.

Cevap

Create an Amazon SQS FIFO queue and configure an AWS Lambda function as the consumer. Send the events to the queue using the patient ID as the message group ID.
The correct solution uses an Amazon SQS FIFO queue with the patient ID as the message group ID. This setup guarantees that all messages belonging to the same patient (the same message group) are processed sequentially, while allowing different patient groups to be processed in parallel. Using AWS Lambda as a consumer provides automatic scaling and minimal operational overhead.

Adım Adım Çözüm

1
Identify the primary requirement for message ordering and concurrency.
Events for the same patient must be processed in order, while events for different patients can be processed concurrently.
This dictates that we need a messaging system that supports message ordering groups.
2
Evaluate Amazon SQS FIFO queues for this scenario.
SQS FIFO queues preserve message order within a specific MessageGroupId.
Using patient ID as the MessageGroupId ensures that all events for a single patient are processed in the order they are received, while allowing concurrent processing of different patient IDs.
3
Compare SQS FIFO with SQS Standard and Amazon Kinesis.
Standard SQS does not guarantee ordering. Kinesis requires partition key design and manual shard scaling.
SQS FIFO provides a serverless, zero-overhead solution for message grouping and ordering, minimizing operational overhead.

Anahtar Kavram

Amazon SQS FIFO queues use the MessageGroupId parameter to group messages that must be processed in a strict sequence, allowing multiple consumers to process different message groups concurrently.
Soru 19Soru

A company runs a high-traffic web application on a fleet of Amazon EC2 instances managed by an Auto Scaling group (ASG). The application is configured to listen on custom port 8080. The instances are registered with a target group behind an Application Load Balancer (ALB) that routes external traffic from port 443 to the target group. A solutions architect must configure health checks to ensure that the ASG accurately detects and replaces instances that fail at the application layer, while maintaining a secure and highly available setup.

Which configuration should the solutions architect implement?

Cevabı ve açıklamayı göster

Cevap: Configure the target group health check to query the application's status path on port 8080, and update the Auto Scaling group to use Elastic Load Balancing (ELB) health checks. Ensure the security groups allow traffic from the ALB to the instances on port 8080.

Cevap

Configure the target group health check to query the application's status path on port 8080, and update the Auto Scaling group to use Elastic Load Balancing (ELB) health checks. Ensure the security groups allow traffic from the ALB to the instances on port 8080.
Configuring the target group health check to query the status path on port 8080 ensures that the ALB tests the actual application port. Setting the Auto Scaling group to use ELB health checks allows the ASG to terminate and replace instances that fail the ALB health checks, maintaining resilience at the application layer. Standard security group rules must also allow port 8080 traffic between the ALB and the instances.

Adım Adım Çözüm

1
Configure the target group health check to match the application's listening port.
The target group is configured to query the custom application port (8080) instead of the default HTTP port (80).
The Application Load Balancer needs to verify the health of the application on the specific port where the application service runs, preventing false-negative health statuses.
2
Integrate the Auto Scaling Group health checks with the Elastic Load Balancer.
The Auto Scaling Group is updated to use ELB health checks in addition to standard EC2 instance status checks.
By default, the ASG only monitors EC2 status (e.g., hardware/hypervisor failures). Adding ELB health checks ensures the ASG replaces instances that fail at the application layer.
3
Establish secure network routing rules for health checks and traffic.
Security groups are configured to allow inbound traffic from the ALB on port 8080, and Network ACLs are configured to permit stateless ephemeral return traffic.
Security groups must allow communication between the load balancer and the targets, and stateless Network ACLs must explicitly allow return traffic to avoid blocking connections.

Anahtar Kavram

Aligning target group health checks with custom application ports, enabling ELB health checks in the Auto Scaling group, and satisfying stateful security group and stateless Network ACL rules.
Tahmini Süre:2m 0s
Soru 20Soru

A security architect is designing an access and credentials management solution for a multi-account AWS environment. An application running on Amazon EC2 instances in Account A (111122223333111122223333) must securely retrieve database credentials to connect to a PostgreSQL database in Account B (444455556666444455556666). The database credentials must be rotated every 3030 days without causing application downtime. The solution must adhere to the principle of least privilege, avoid long-term credentials, and ensure all data in transit and at rest is secured using customer-managed keys (CMKs). Which architecture represents the most secure and compliant design that meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Store the credentials in AWS Secrets Manager in Account B, encrypted with a customer-managed KMS key. Attach an IAM role to the EC2 instances in Account A, and configure the Secrets Manager resource policy and the KMS key policy in Account B to permit the Account A role to retrieve the secret and decrypt using the KMS key. Configure automatic rotation in Secrets Manager using a Lambda function in Account B.

Cevap

Store the credentials in AWS Secrets Manager in Account B, encrypted with a customer-managed KMS key. Attach an IAM role to the EC2 instances in Account A, and configure the Secrets Manager resource policy and the KMS key policy in Account B to permit the Account A role to retrieve the secret and decrypt using the KMS key. Configure automatic rotation in Secrets Manager using a Lambda function in Account B.
The correct architecture stores credentials securely in AWS Secrets Manager, which supports automated rotation using a Lambda function. Using resource-based policies on the secret and the KMS key in the database account (Account B) allows the IAM role attached to the EC2 instances in Account A to retrieve and decrypt the secret without needing long-term credentials. This adheres to the principles of least privilege and secure cross-account access.

Adım Adım Çözüm

1
Evaluate credential storage and transmission requirements.
Determine that credentials must be stored securely using AWS Secrets Manager in the database account (Account B) rather than Systems Manager Parameter Store in plaintext, and access must be granted using IAM roles rather than long-term IAM user access keys.
This satisfies the requirements for encryption at rest/in transit, avoiding long-term credentials, and practicing least privilege.
2
Configure cross-account access policies for the EC2 instances.
Grant the EC2 instance role in Account A access to Secrets Manager and KMS in Account B. Ensure the Secrets Manager resource policy and the KMS key policy in Account B explicitly permit the role in Account A.
For cross-account access, resource-based policies (and KMS key policies) must trust the external account or role directly since identity-based policies in Account A alone are insufficient.
3
Configure the automated credential rotation mechanism.
Enable Secrets Manager automatic rotation, which uses a Lambda function to update the database password and the secret value.
AWS KMS key rotation only rotates KMS key material, not the actual secret value. Secrets Manager rotation is required to securely update database credentials.

Anahtar Kavram

Cross-account access and credentials rotation utilizing AWS Secrets Manager and AWS KMS with resource-based policies.
Tahmini Süre:3m 0s
Sayfa 1 / 37Sonraki