Tüm alıştırma soruları

976 soru

Soru 561Soru

A SysOps Administrator is configuring AWS Systems Manager Patch Manager to automate security updates for a fleet of Amazon Linux 2 EC2 instances. The instances run in a private VPC subnet with no internet connectivity. To allow communication with Systems Manager, the administrator successfully creates interface VPC endpoints for ssm, ssmmessages, and ec2messages. However, when the automated patching task runs, the instances fail to download the required OS update packages, and the patching execution fails. Which of the following should the administrator do to resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Create a gateway VPC endpoint for Amazon S3 and associate it with the route table of the private subnet.

Cevap

Create a gateway VPC endpoint for Amazon S3 and associate it with the route table of the private subnet.
Amazon Linux 2 package repositories are hosted in Amazon S3 buckets. In a private subnet with no internet access, instances can communicate with the Systems Manager service via interface VPC endpoints, but they cannot download the actual patch files from Amazon S3 without a route to S3. Creating a gateway VPC endpoint for Amazon S3 and associating it with the private subnet's route table allows the instances to securely download the update packages entirely within the AWS network.

Adım Adım Çözüm

1
Identify the repository hosting locations for Amazon Linux 2 updates.
The package repositories for Amazon Linux 2 are hosted on AWS-managed S3 buckets in the local region.
Understanding where the patches are downloaded from helps isolate why the download phase is failing.
2
Analyze network pathing for S3 access from a private subnet.
Interface endpoints for ssm only cover service control communications, not the binary package downloads from S3.
Determining that a private path to S3 is required to securely download packages without an internet gateway.
3
Configure a gateway VPC endpoint for S3 and link it to the subnet's route table.
A route targeting the S3 prefix list is added to the private subnet's route table, allowing instances to reach the repository.
This establishes the necessary private routing to download patch binaries successfully.

Anahtar Kavram

Enabling S3 access for SSM Patch Manager in a private VPC subnet using Gateway Endpoints.
Soru 562Soru

A SysOps Administrator is configuring cross-account access to a customer managed KMS key in Account A (123456789012123456789012) to allow an application running on an IAM role in Account B (987654321098987654321098) to decrypt data.

Currently, the KMS key policy in Account A contains the following default statement:

{
"Sid": "Enable IAM User Permissions",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::123456789012:root"
},
"Action": "kms:*",
"Resource": "*"
}

Which combination of actions must the SysOps Administrator perform to grant the application in Account B access to the KMS key? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: In Account A, modify the customer managed KMS key policy to grant the Account B AWS account root principal (`arn:aws:iam::987654321098:root`) permission to perform the `kms:Decrypt` action.; In Account B, attach an IAM policy to the application's IAM role that allows the `kms:Decrypt` action on the KMS key ARN in Account A.

Cevap

In Account A, modify the customer managed KMS key policy to grant the Account B AWS account root principal permission to perform the `kms:Decrypt` action; and in Account B, attach an IAM policy to the application's IAM role that allows the `kms:Decrypt` action on the KMS key ARN in Account A.
For cross-account access to a customer managed AWS KMS key, both accounts must grant permissions. The owning account (Account A) must update the KMS key policy to trust the consuming account (Account B) root principal or the specific IAM role. The consuming account (Account B) must then grant permission to the IAM role via an identity-based IAM policy targeting the KMS key's Amazon Resource Name (ARN).

Adım Adım Çözüm

1
Modify the key policy in the key-owning account (Account A) to trust the external account's root principal (`arn:aws:iam::987654321098:root`) or the specific IAM role.
This establishes the trust relationship from the resource owner side, enabling delegation.
By default, KMS key policies restrict access to the host account. Cross-account access requires explicit resource-level permission in the key policy.
2
Attach an identity-based IAM policy to the IAM role in Account B allowing `kms:Decrypt` on the specific key ARN in Account A.
This grants the application's role the client-side permission to call the external KMS key.
Even if the key policy trusts Account B, the target IAM role in Account B must be explicitly permitted to perform the action in its own identity policy.

Anahtar Kavram

AWS KMS cross-account access requires authorization from both the resource-based key policy in the owning account and the identity-based IAM policy in the consuming account.
Soru 563Soru

A SysOps Administrator is responsible for managing the OS updates for a fleet of Amazon EC2 instances running Red Hat Enterprise Linux (RHEL). The fleet consists of two environments: development and production. The administrator needs to automate the patching process using AWS Systems Manager Patch Manager so that development instances are patched using a custom baseline named RHEL-Dev-Baseline, and production instances are patched using a custom baseline named RHEL-Prod-Baseline. Patches must be applied automatically during separate weekly maintenance windows. Which two actions must the SysOps Administrator perform to ensure the correct baseline is applied to each environment during their scheduled maintenance windows? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Apply a tag to the EC2 instances with the key 'Patch Group' and set the value to 'Dev-Patch-Group' for development instances and 'Prod-Patch-Group' for production instances.; In Systems Manager Patch Manager, associate the RHEL-Dev-Baseline with the Dev-Patch-Group patch group, and the RHEL-Prod-Baseline with the Prod-Patch-Group patch group.

Cevap

Apply a tag to the EC2 instances with the key 'Patch Group' and set the value to 'Dev-Patch-Group' for development instances and 'Prod-Patch-Group' for production instances. In Systems Manager Patch Manager, associate the RHEL-Dev-Baseline with the Dev-Patch-Group patch group, and the RHEL-Prod-Baseline with the Prod-Patch-Group patch group.
To apply custom baselines to specific EC2 instances, the instances must be grouped into patch groups by applying a resource tag with the key 'Patch Group'. Then, the custom patch baselines must be explicitly associated with these patch groups in Systems Manager Patch Manager. When the maintenance window task runs the patching document, Systems Manager checks the 'Patch Group' tag of the target instances, identifies the associated baseline, and applies the updates accordingly.

Adım Adım Çözüm

1
Tag the target EC2 instances with the system-defined tag key 'Patch Group' using values matching the development and production groups.
Instances are logical members of their respective patch groups.
Systems Manager uses this specific tag key to assign instances to patch groups.
2
Associate each custom patch baseline with its corresponding patch group in the Systems Manager console or using the AWS CLI register-patch-baseline-for-patch-group command.
Custom patch baselines are mapped to Dev-Patch-Group and Prod-Patch-Group.
This configuration overrides the region-wide default patch baseline for these specific groups.
3
Register Maintenance Window tasks targeting the patch groups and ensure the registering user has the necessary iam:PassRole permissions for the service role.
The automated maintenance window execution succeeds and applies the correct baseline to each environment.
The iam:PassRole permission allows Systems Manager to run the patch task on behalf of the administrator using the specified service role.

Anahtar Kavram

Systems Manager Patch Manager uses the case-sensitive tag key 'Patch Group' to map instances to patch groups, which are then associated with custom patch baselines. The execution of these automated updates requires proper iam:PassRole authorization for Maintenance Window tasks.
Tahmini Süre:1m 30s
Soru 564Soru

An organization's web application is hosted on Amazon EC2 instances behind an Application Load Balancer (ALB). The application receives traffic forwarded from a third-party Content Delivery Network (CDN) provider. A SysOps administrator is configuring an AWS WAF Web ACL associated with the ALB to mitigate brute-force attempts on the login portal located at /admin/login. Because the CDN routes all traffic, the source IP of all incoming HTTP requests to the ALB is that of the CDN edge servers. The client's actual IP address is preserved in the X-Forwarded-For HTTP header.

Which of the following configuration steps should the administrator perform on the rate-based rule to block malicious clients while minimizing impact on legitimate traffic? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Configure the rate-based rule to evaluate the IP address found in the X-Forwarded-For header.; Define a scope-down statement within the rate-based rule to only match requests where the URI path is /admin/login.

Cevap

To mitigate the brute-force attempts under these conditions, configure the rate-based rule to evaluate the IP address found in the X-Forwarded-For header, and define a scope-down statement within the rate-based rule to only match requests where the URI path is /admin/login.
Evaluating the IP address in the X-Forwarded-For header is required to correctly identify the client when a CDN proxy sits in front of the application. Additionally, a scope-down statement targeting the /admin/login path ensures that the rate limit only tracks requests to the login page, protecting the rest of the application from inadvertent blocks.

Adım Adım Çözüm

1
Configure the rate-based rule IP source evaluation settings.
AWS WAF is set to parse the IP address in the X-Forwarded-For HTTP header.
Since traffic is routed through a third-party CDN, the default source IP option would incorrectly count all requests as originating from the CDN edge server. Using the header evaluates the actual client IP.
2
Add a scope-down statement to the rate-based rule configuration.
The rate-based rule only counts requests matching the specified URI path constraint.
Applying the rate limit without a scope-down statement would count all requests to any page on the web application, leading to false-positive blocks for legitimate users who browse multiple pages.

Anahtar Kavram

Configuring AWS WAF rate-based rules with forwarded IP headers and scope-down statements in proxied environments.
Soru 565Soru

An administrator deploys web servers in a subnet of a new VPC (10.0.0.0/1610.0.0.0/16). The servers must host a public website on port 8080 and retrieve updates from a public third-party repository. The instances have public IPv4 addresses. Currently, users on the internet cannot access the website, and the web servers cannot reach the external repository.

The administrator verifies the following configuration details:
- The security group associated with the web servers allows inbound port 8080 from 0.0.0.0/00.0.0.0/0 and all outbound traffic.
- The custom Network Access Control List (NACL) associated with the subnet has inbound rules allowing port 8080 from 0.0.0.0/00.0.0.0/0 and outbound rules allowing all traffic to 0.0.0.0/00.0.0.0/0.
- The subnet's route table contains a local route for 10.0.0.0/1610.0.0.0/16 but no other routes. An Internet Gateway is attached to the VPC.

Which combination of actions will resolve the connectivity issues? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Add a route to the subnet's route table for 0.0.0.0/00.0.0.0/0 targeting the Internet Gateway.; Add an inbound rule to the custom NACL allowing traffic from 0.0.0.0/00.0.0.0/0 on ephemeral ports (10241024-6553565535).

Cevap

Add a route to the subnet's route table for 0.0.0.0/00.0.0.0/0 targeting the Internet Gateway, and add an inbound rule to the custom NACL allowing traffic from 0.0.0.0/00.0.0.0/0 on ephemeral ports (10241024-6553565535).
To resolve the issues, the administrator must address two distinct bottlenecks: routing and stateless firewall rules. First, a route for 0.0.0.0/00.0.0.0/0 targeting the Internet Gateway is required in the subnet's route table to establish a path to the internet. Second, because NACLs are stateless, return traffic for connections initiated by the web servers (such as updates from the repository) will target the web servers' ephemeral ports (10241024-6553565535). Thus, an inbound rule allowing traffic on ephemeral ports is required to permit this response traffic.

Adım Adım Çözüm

1
Analyze the routing table configuration.
The routing table only contains a local route (10.0.0.0/1610.0.0.0/16), meaning the instances have no way to route traffic out to the internet.
Public subnet communication requires a default route (0.0.0.0/00.0.0.0/0) pointing to the Internet Gateway (IGW).
2
Analyze the stateless firewall (NACL) rules for outbound connections initiated by the web servers.
When the web servers initiate outbound connections to the external repository on ports 8080 or 443443, the return packets from the repository target the client's temporary ephemeral ports (10241024-6553565535). Since the custom NACL only allows inbound traffic on port 8080, these return packets are blocked.
Network ACLs are stateless and require explicit rules for both request and response traffic in both directions.
3
Evaluate the proposed solutions against security group and routing requirements.
Adding the 0.0.0.0/00.0.0.0/0 route to the IGW enables outbound routing. Adding the inbound NACL rule for ephemeral ports (10241024-6553565535) enables the return traffic for connections initiated by the servers. Security Group modifications are unnecessary due to statefulness.
Both routing and stateless firewall constraints must be resolved to restore complete internet connectivity.

Anahtar Kavram

SysOps administrators must configure both routing tables and stateless network access control lists (NACLs) to enable two-way internet communication in a VPC subnet.
Soru 566Soru

A SysOps Administrator is configuring Amazon EC2 instances in a private subnet with no internet access to retrieve container images from Amazon Elastic Container Registry (Amazon ECR). The administrator creates Interface Endpoints for com.amazonaws.us-east-1.ecr.dkr and com.amazonaws.us-east-1.ecr.api in the VPC and enables private DNS. However, the instances still fail to pull container images, and the pull process times out when trying to download the image layers. Which action should the SysOps Administrator take to resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Create a Gateway Endpoint for Amazon S3 and associate it with the route table of the private subnet.

Cevap

Create a Gateway Endpoint for Amazon S3 and associate it with the route table of the private subnet.
The correct answer is to create a Gateway Endpoint for Amazon S3 and associate it with the route table of the private subnet. Although Amazon ECR API commands and image manifests are accessed via ECR Interface Endpoints, the actual image layers are stored in Amazon S3. In a completely private subnet, the instances need private access to both ECR and S3. Creating and properly associating the S3 Gateway Endpoint ensures the instances can download the image layers.

Adım Adım Çözüm

1
Identify the destination that is causing the timeout during the container image pull process.
Amazon ECR uses Amazon S3 under the hood to store and serve the actual image layers.
Understanding where the layer data is hosted helps target the correct endpoint configuration.
2
Establish private connectivity to Amazon S3 within the isolated VPC.
Create a Gateway Endpoint for Amazon S3.
A Gateway Endpoint provides direct, private connectivity to S3 without requiring an internet gateway or NAT gateway.
3
Associate the newly created Amazon S3 Gateway Endpoint with the route table of the private subnet containing the EC2 instances.
A route is automatically added to the route table directing S3-destined traffic through the Gateway Endpoint.
Without this association, the instances' traffic destined for S3 will not be routed to the endpoint, resulting in continued timeouts.

Anahtar Kavram

VPC Endpoints and PrivateLink Integration
Soru 567Soru

A company's web application is distributed globally using an Amazon CloudFront distribution protected by an AWS WAF web ACL. The application has recently experienced an HTTP flood attack targeting the feedback submission endpoint at `/submit-feedback`. A SysOps administrator needs to configure AWS WAF to block requests to `/submit-feedback` from any client IP address that exceeds 200 requests within a 5-minute period, while ensuring that legitimate traffic to other pages and endpoints on the website is not rate-limited or blocked.

Which configuration should the SysOps administrator implement to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Create an AWS WAF rate-based rule with a rate limit of 200. Configure a scope-down statement within the rule to only inspect requests where the URI path matches `/submit-feedback`, and set the rule action to Block.

Cevap

Create an AWS WAF rate-based rule with a rate limit of 200. Configure a scope-down statement within the rule to only inspect requests where the URI path matches `/submit-feedback`, and set the rule action to Block.
The correct configuration is to implement a rate-based rule with a scope-down statement. AWS WAF rate-based rules track the number of incoming requests from each IP address over a sliding 5-minute window. By adding a scope-down statement matching the `/submit-feedback` URI, the administrator ensures that the rate limit of 200 is only counted against requests heading to that specific endpoint. Once a client IP exceeds this threshold, AWS WAF blocks further requests from that IP address, preventing the resource exhaustion attack while leaving other traffic untouched.

Adım Adım Çözüm

1
Open the AWS WAF console, locate the web ACL associated with the Amazon CloudFront distribution, and add a custom rule.
A new custom rule definition wizard is opened within the selected web ACL.
AWS WAF web ACLs must be modified to apply new rules protecting the CloudFront distribution.
2
Define the rule type as a 'Rate-based rule' and set the rate limit threshold to 200 requests per 5 minutes.
AWS WAF is configured to track incoming request rates for individual client IP addresses.
This sets the threshold for rate-limiting, which dictates when a client IP will be blocked.
3
Configure a scope-down statement inside the rate-based rule with a condition matching the URI path equal to `/submit-feedback`.
AWS WAF only increments the request counter for a client IP when that client accesses the specific path.
This ensures that traffic to other parts of the website is excluded from the rate-limiting calculations, preventing false positives for normal users browsing the site.
4
Set the default rule action to 'Block' and save the rule.
The rule is deployed to the edge locations, blocking traffic from offending IPs to the `/submit-feedback` page once they exceed the limit.
This mitigates the HTTP flood attack at the AWS edge before it reaches the backend origin servers.

Anahtar Kavram

AWS WAF Rate-Based Rules and Scope-Down Statements
Soru 568Soru

A company hosts several testing workloads in a development AWS account. Due to the ad-hoc nature of these tests, resource utilization fluctuates wildly, resulting in highly variable and unpredictable daily spending. The SysOps administrator must set up a solution that uses machine learning to automatically detect unexpected cost anomalies and immediately send alert notifications to the operations team's Slack channel. Which solution will meet these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Create an AWS Cost Anomaly Monitor for the account, configure an alert subscription, and integrate it with AWS Chatbot to deliver notifications to the Slack channel.

Cevap

Create an AWS Cost Anomaly Monitor for the account, configure an alert subscription, and integrate it with AWS Chatbot to deliver notifications to the Slack channel.
The correct solution leverages AWS Cost Anomaly Detection, which uses machine learning to dynamically model spend profiles and eliminate false positives from variable workloads. It then routes notifications natively through AWS Chatbot directly to Slack, resulting in the lowest possible operational overhead.

Adım Adım Çözüm

1
Select a cost-monitoring service that utilizes machine learning for variable spend.
Choose AWS Cost Anomaly Detection.
Unlike static budgets, Cost Anomaly Detection uses machine learning to dynamically establish baselines and adjust to irregular usage patterns, minimizing false-alarm fatigue.
2
Determine the lowest-overhead method to route alerts to Slack.
Use AWS Chatbot integrated with Cost Anomaly Detection subscriptions.
AWS Chatbot natively supports AWS Cost Anomaly Detection alert subscriptions and can format and post messages to Slack directly, eliminating the need to write and maintain custom integration code.

Anahtar Kavram

AWS Cost Anomaly Detection uses machine learning models to detect unexpected spikes in spending while AWS Chatbot provides native integration to deliver these alerts to chat channels with minimal configuration.
Tahmini Süre:1m 30s
Soru 569Soru

A SysOps Administrator is configuring a customer managed KMS key to encrypt an Amazon S3 bucket in the same AWS account. An IAM user named DataAuditor needs to decrypt objects in this bucket. The administrator has attached an IAM policy to the DataAuditor user that allows kms:Decrypt on the KMS key's ARN. However, the user still receives an Access Denied error when trying to download and decrypt the objects. The current KMS key policy has been modified and does not contain the default statement that enables IAM policies.

Which of the following actions will resolve this issue? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Modify the KMS key policy to explicitly grant the kms:Decrypt permission to the DataAuditor IAM user.; Add a statement to the KMS key policy that grants the AWS account root principal (arn:aws:iam::111122223333:root) permissions to perform all KMS actions.

Cevap

Modify the KMS key policy to explicitly grant the kms:Decrypt permission to the DataAuditor IAM user, or add a statement to the KMS key policy that grants the AWS account root principal permissions to perform all KMS actions.
For customer managed KMS keys, the key policy is the primary controller of access. If the default statement delegating permissions to the account root principal is missing, IAM policies alone cannot grant access. To resolve this, you must either modify the KMS key policy to directly grant the user kms:Decrypt permissions, or add a statement to the KMS key policy that grants the AWS account root principal permissions, which enables the user's IAM policy to take effect.

Adım Adım Çözüm

1
Analyze KMS evaluation logic.
Confirm that KMS key policies are the primary authenticator. Without delegation to the account root principal, IAM policies targeting the KMS key will be ignored.
This identifies why the user's current IAM policy is not sufficient to grant access.
2
Select resolution methods.
Determine that either the key policy must explicitly authorize the user, or it must delegate authority back to IAM policies by authorizing the account's root user.
These are the two standard paths to grant key usage permissions in AWS KMS.

Anahtar Kavram

AWS KMS evaluation logic requires either explicit key policy permission or delegation to IAM policies via the account root principal in the key policy.
Soru 570Soru

A company runs a web application with endpoints in the `us-east-1` Region, the `us-west-2` Region, and an on-premises data center in Chicago. A SysOps administrator must configure Amazon Route 53 to route client traffic to the closest physical endpoint. During scheduled maintenance of the Chicago data center, the administrator needs to redirect a portion of the traffic that would normally route to Chicago to the `us-east-1` Region instead, without altering the DNS endpoint IP addresses or physical locations.

Which Route 53 configuration should the SysOps administrator use to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure a Geoproximity routing policy using Route 53 Traffic Flow. Define the endpoints for the AWS Regions and specify the latitude and longitude coordinates for the Chicago data center. To shift traffic away from Chicago to the `us-east-1` Region, apply a negative bias to the Chicago endpoint and a positive bias to the `us-east-1` endpoint.

Cevap

Configure a Geoproximity routing policy using Route 53 Traffic Flow. Define the endpoints for the AWS Regions and specify the latitude and longitude coordinates for the Chicago data center. To shift traffic away from Chicago to the `us-east-1` Region, apply a negative bias to the Chicago endpoint and a positive bias to the `us-east-1` endpoint.
The correct option outlines configuring a Geoproximity routing policy using Route 53 Traffic Flow, mapping the on-premises coordinates, and applying a negative bias to the Chicago endpoint alongside a positive bias to the `us-east-1` endpoint. Geoproximity routing requires Route 53 Traffic Flow and supports specifying coordinates for non-AWS resources. Applying a negative bias shrinks the routing footprint of the Chicago endpoint, while a positive bias expands the routing footprint of the `us-east-1` endpoint, successfully shifting traffic.

Adım Adım Çözüm

1
Analyze routing requirements
The requirement demands routing users to the closest physical endpoint among AWS regions and a non-AWS on-premises endpoint, with the ability to dynamically shift boundaries.
Geoproximity routing is the only policy that calculates routing based on coordinates and allows shifting traffic using bias values.
2
Select configuration method and define coordinates
Geoproximity routing must be configured using Route 53 Traffic Flow. Specify the AWS Regions directly and the latitude and longitude coordinates for the Chicago data center.
Route 53 standard DNS records do not support Geoproximity routing, and coordinates are required to calculate proximity for non-AWS targets.
3
Adjust bias settings to shift traffic
Apply a negative bias to the Chicago endpoint to shrink its geographic footprint, and a positive bias to the `us-east-1` endpoint to expand its footprint.
A positive bias (11 to 9999) expands a region's routing footprint, while a negative bias (1-1 to 99-99) shrinks it, effectively shifting the boundaries of user requests.

Anahtar Kavram

Amazon Route 53 Geoproximity routing policy using Traffic Flow and bias adjustments for hybrid endpoints.
Tahmini Süre:2m 0s
Soru 571Soru

A SysOps Administrator is tasked with automating the deployment of OS patches for a fleet of Amazon Linux 2023 EC2 instances. The administrator wants to use a custom patch baseline to enforce security compliance. The instances are divided into a 'Production' environment, and patches must only be applied during a weekly Saturday night maintenance window. The setup must ensure that the custom baseline is applied rather than the default AWS-managed baseline. Arrange the steps in the correct order to configure this automated patch management workflow.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct order of steps is: 1) Create a custom patch baseline for Amazon Linux 2023. 2) Associate the patch group named 'Production' with the custom patch baseline. 3) Apply the case-sensitive tag key 'Patch Group' with value 'Production' to the EC2 instances. 4) Create a Systems Manager Maintenance Window. 5) Register targets and the AWS-RunPatchBaseline task to the Maintenance Window.
The correct order follows the logical dependencies of Systems Manager resources. First, the custom patch baseline is created to define rules. Second, the patch group name is associated with the baseline so that when instances register to the group, Systems Manager knows which baseline to apply. Third, the 'Patch Group' tag is applied to instances. Fourth, a Maintenance Window is defined to control the schedule. Finally, targets and the 'AWS-RunPatchBaseline' task are registered within the Maintenance Window.

Adım Adım Çözüm

1
Create the custom patch baseline.
A custom baseline with custom approval rules is created.
This establishes the compliance rules for Amazon Linux 2023 before any association can occur.
2
Associate the 'Production' patch group string with the custom patch baseline.
The patch group is bound to the custom baseline.
This ensures any instance belonging to the 'Production' patch group uses the custom baseline rather than the default baseline.
3
Tag the EC2 instances with the case-sensitive tag key 'Patch Group' and value 'Production'.
The instances are grouped under the 'Production' patch group.
This assigns the instances to the correct baseline and allows them to be targeted together.
4
Create a Systems Manager Maintenance Window.
A scheduled window is defined.
A Maintenance Window must exist before targets and tasks can be registered under it.
5
Register the target instances and the 'AWS-RunPatchBaseline' task in the Maintenance Window.
The automated patching workflow is fully configured.
This links the schedule, the target instances, and the patching command to execute the updates.

Anahtar Kavram

Orchestrating automated patching using Systems Manager Patch Manager custom baselines, patch groups, and maintenance windows.
Tahmini Süre:2m 0s
Soru 572Soru

A company's production e-commerce application is hosted on Amazon EC2 instances behind an Application Load Balancer (ALB). The company has subscribed to AWS Shield Advanced to protect its infrastructure from distributed denial of service (DDoS) attacks. A SysOps administrator is tasked with configuring automatic application-layer DDoS mitigation to block traffic from sources identified by AWS Shield.

Which two configuration steps must the administrator perform to enable this automatic mitigation? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Associate an AWS WAF Web ACL with the Application Load Balancer.; Enable automatic application-layer DDoS mitigation on the protected ALB resource within AWS Shield Advanced.

Cevap

Associate an AWS WAF Web ACL with the Application Load Balancer, and enable automatic application-layer DDoS mitigation on the protected ALB resource within AWS Shield Advanced.
To protect an Application Load Balancer with AWS Shield Advanced automatic application-layer DDoS mitigation, the administrator must first ensure an AWS WAF Web ACL is associated with the ALB. The administrator must then enable the automatic mitigation option on the protected resource in Shield Advanced. When enabled, Shield Advanced automatically creates the 'ShieldMitigationRuleGroup' inside the associated Web ACL and dynamically updates rules during an event to block malicious traffic.

Adım Adım Çözüm

1
Ensure the Application Load Balancer is protected by AWS Shield Advanced and associated with an AWS WAF Web ACL.
The ALB resource is configured to be monitored by Shield Advanced and has a Web ACL attached.
AWS Shield Advanced requires an associated WAF Web ACL to automatically insert and manage mitigation rules.
2
Enable the automatic application-layer DDoS mitigation setting in the AWS Shield Advanced console or via the AWS CLI for the protected ALB resource.
AWS Shield Advanced automatically creates and configures the 'ShieldMitigationRuleGroup' inside the associated Web ACL.
This allows AWS Shield to dynamically add WAF rules to block traffic from identified DDoS sources in response to an ongoing attack.

Anahtar Kavram

AWS Shield Advanced Automatic Application-Layer DDoS Mitigation
Soru 573Soru

A SysOps Administrator is configuring an Amazon SQS queue in AWS account `111122223333` to use server-side encryption with a customer managed KMS key. An application running on an Amazon EC2 instance in the same account must send messages to the queue. The administrator has attached an IAM policy to the EC2 instance profile's IAM role that grants `sqs:SendMessage`, `kms:GenerateDataKey`, and `kms:Decrypt` permissions. However, the application logs show an Access Denied error when attempting to send messages to the queue.

The customer managed KMS key's key policy is configured as follows:

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Allow Key Administration",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::111122223333:user/SecurityAdmin"
},
"Action": "kms:*",
"Resource": "*"
}
]
}

Which modification must the administrator make to resolve this access issue?

Cevabı ve açıklamayı göster

Cevap: Add a statement to the KMS key policy that grants the AWS account root principal (`arn:aws:iam::111122223333:root`) access to the key, thereby enabling the IAM policy attached to the EC2 instance profile's role to take effect.

Cevap

Add a statement to the KMS key policy that grants the AWS account root principal (`arn:aws:iam::111122223333:root`) access to the key, thereby enabling the IAM policy attached to the EC2 instance profile's role to take effect.
To allow IAM policies to grant access to a customer managed KMS key, the key policy must explicitly delegate authorization to the account. This is accomplished by adding a statement to the key policy that grants the AWS account root principal (`arn:aws:iam::111122223333:root`) access to the key. Once this delegation is in place, the IAM policy attached to the EC2 instance profile's role can successfully grant the application permission to use the KMS key for encryption and decryption.

Adım Adım Çözüm

1
Inspect the customer managed KMS key policy to check for IAM delegation.
Identify that the key policy only grants access to `arn:aws:iam::111122223333:user/SecurityAdmin` and lacks a statement delegating permissions to the root principal (`arn:aws:iam::111122223333:root`).
By default, customer managed KMS keys are only accessible via their key policy unless IAM delegation is enabled.
2
Determine the correct way to allow IAM policies to authorize KMS actions on the key.
Conclude that adding a statement to the key policy that allows the root principal (`arn:aws:iam::111122223333:root`) to perform KMS actions is required.
This enables the KMS service to evaluate the IAM policy attached to the EC2 instance profile's role when evaluating the request.

Anahtar Kavram

KMS Key Policy Delegation to IAM Policies
Soru 574Soru

A company manages a fleet of Amazon EC2 instances running SUSE Linux Enterprise Server (SLES) split into Development and Production environments. A SysOps Administrator creates a custom patch baseline for SLES and registers a patch group named 'SLES-Dev' to this baseline. The administrator tags the Development EC2 instances with a tag key of 'Patch_Group' and a value of 'SLES-Dev'. A Systems Manager Maintenance Window is configured to run patch operations targeting these instances. During the next scheduled maintenance window, the administrator notices that the Development instances are patched using the default AWS-managed SLES patch baseline instead of the custom patch baseline. Which of the following explains why the Development instances were patched using the default baseline?

Cevabı ve açıklamayı göster

Cevap: The tag key on the EC2 instances must be defined as 'Patch Group' instead of 'Patch_Group'.

Cevap

The tag key on the EC2 instances must be defined as 'Patch Group' instead of 'Patch_Group'.
Systems Manager Patch Manager relies on a specific tag key named 'Patch Group' (case-sensitive, containing a space) to map EC2 instances to defined patch groups. Because the administrator used 'Patch_Group' (with an underscore), Patch Manager failed to recognize the mapping. Consequently, the instances were not associated with the 'SLES-Dev' patch group, causing Patch Manager to fall back to the default AWS-managed patch baseline for SLES.

Adım Adım Çözüm

1
Identify the mechanism Systems Manager Patch Manager uses to associate EC2 instances with patch groups.
Patch Manager checks for the Amazon EC2 resource tag key 'Patch Group' (case-sensitive and containing a space).
This specific key is required by AWS Systems Manager to parse patch group associations.
2
Analyze the tag configuration applied to the Development instances.
The instances were tagged with 'Patch_Group' (using an underscore).
To evaluate if the configuration matches the Systems Manager requirement.
3
Determine the consequence of the mismatched tag key.
Patch Manager fails to map the instances to the 'SLES-Dev' patch group and falls back to using the default patch baseline.
When no patch group is recognized, Systems Manager defaults to the default baseline defined for that operating system.

Anahtar Kavram

Systems Manager Patch Group Tagging Requirements
Soru 575Soru

A SysOps administrator is managing a web application's regional REST API hosted on Amazon API Gateway. During peak traffic hours, the API suffers from performance degradation due to a high volume of HTTP flood requests originating from a distributed set of IP addresses. The administrator needs to configure AWS WAF to mitigate these web-layer DDoS attacks. Additionally, to comply with strict storage cost optimization guidelines, only requests that are actively blocked by AWS WAF rules must be logged.

Which TWO configuration steps must the SysOps administrator implement to meet these requirements? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Add a rate-based rule to the Web ACL that evaluates requests based on the client IP address, and set the rule action to Block.; Enable logging for the Web ACL and configure a logging filter that specifies a rule action of Block as the logging condition.

Cevap

The SysOps administrator should add a rate-based rule to the Web ACL to block clients exceeding request thresholds, and enable logging for the Web ACL with a logging filter that only records requests with a Block action.
To mitigate HTTP flood attacks from a distributed set of IP addresses, a rate-based rule should be added to the Web ACL to automatically track request rates and block IPs that exceed the threshold. To optimize storage costs, a logging filter should be set up on the Web ACL to specify that only requests matching the Block action are published to the log destination, dropping all other allowed traffic logs.

Adım Adım Çözüm

1
Implement threat protection using AWS WAF by creating a rate-based rule to monitor request volumes from individual IP addresses over a sliding window, blocking those that exceed the limit.
Dynamic client IP addresses causing the HTTP flood are automatically throttled and blocked.
Rate-based rules are the standard AWS WAF feature for mitigating application-layer (Layer 7) DDoS/HTTP flood attacks.
2
Configure AWS WAF logging and direct the logs to a supported destination (such as CloudWatch Logs, an S3 bucket, or Kinesis Data Firehose).
A logging pipeline is established to capture Web ACL request metadata.
Logging must be enabled on the Web ACL before filters can be applied to manage the destination data volume.
3
Define a logging filter on the Web ACL configuration that evaluates the rule action of each request and drops logs that do not match the Block action.
Only log entries for requests blocked by AWS WAF are published to the destination, filtering out allowed traffic logs.
This configuration minimizes log storage requirements and associated costs by preventing allowed traffic logs from being generated.

Anahtar Kavram

AWS WAF threat mitigation via rate-based rules combined with logging cost optimization using logging filters.
Soru 576Soru

A company wants to implement a machine learning-based monitoring solution to identify unexpected cost spikes at the individual AWS service level. Once an anomaly is detected, the SysOps team needs to receive immediate notifications in their Microsoft Teams channel. Which of the following steps are required to implement this solution? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Create an AWS services cost monitor in AWS Cost Anomaly Detection.; Create an alert subscription linked to the monitor, select an Amazon SNS topic as the alert destination, and configure AWS Chatbot to integrate the SNS topic with Microsoft Teams.

Cevap

To monitor individual service costs and alert via Microsoft Teams, you must create an AWS services cost monitor in AWS Cost Anomaly Detection, and create an alert subscription that routes notifications to an Amazon SNS topic, which AWS Chatbot then delivers to the Microsoft Teams channel.
To monitor anomalous spend at the service level, you must create an 'AWS services' monitor in AWS Cost Anomaly Detection. Because Cost Anomaly Detection alert subscriptions only support Amazon SNS and email as destinations, sending alerts to Microsoft Teams requires routing through an Amazon SNS topic. AWS Chatbot can then be configured to subscribe to this SNS topic and deliver the alerts directly to the designated Microsoft Teams channel.

Adım Adım Çözüm

1
Configure the cost monitor
An AWS services cost monitor is created in AWS Cost Anomaly Detection to monitor spend patterns across individual AWS services using machine learning.
This establishes the detection mechanism tailored to individual service-level spend rather than total account spend or cost categories.
2
Configure the alert subscription
An alert subscription is created in AWS Cost Anomaly Detection and mapped to an Amazon SNS topic.
Since Cost Anomaly Detection subscriptions do not support direct webhook integrations, Amazon SNS must act as the message broker.
3
Configure the chat integration
AWS Chatbot is configured to target the Microsoft Teams channel and is subscribed to the Amazon SNS topic.
This enables AWS Chatbot to receive the cost anomaly events from SNS and formats them as rich alerts in Microsoft Teams.

Anahtar Kavram

Integrating AWS Cost Anomaly Detection with AWS Chatbot and Amazon SNS for automated chat-based alerting on service-level cost anomalies.
Soru 577Soru

An administrator is troubleshooting an application running on an Amazon EC2 instance that needs to decrypt sensitive database backups retrieved from an Amazon S3 bucket. The backups are encrypted using a customer managed KMS key. Although the administrator has attached an IAM policy to the EC2 instance's IAM role that grants `kms:Decrypt` permissions for the key's Amazon Resource Name (ARN), the application still receives an Access Denied error when attempting to decrypt.

Which of the following configuration changes or verifications must the administrator perform to resolve this issue? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Verify that the KMS key policy contains a statement that allows the EC2 instance's IAM role, or the account's root principal, to perform the `kms:Decrypt` action.; Verify that the customer managed KMS key is in the Enabled state and has not been disabled or scheduled for deletion.

Cevap

To resolve the decryption failure, the administrator must verify that the KMS key policy permits access (either directly or via IAM delegation) and ensure that the key is in the Enabled state.
The correct configurations involve ensuring that the key policy delegates access to IAM policies or the specific principal, and that the key is in the Enabled state. For customer managed keys, the key policy is the ultimate authority; IAM policies cannot grant access to a KMS key unless the key policy explicitly allows it (often by granting access to the root account principal). Furthermore, a KMS key must be enabled to perform cryptographic operations like decryption.

Adım Adım Çözüm

1
Analyze the KMS key policy configuration.
Determine if the key policy delegates authority to IAM policies or directly trusts the EC2 instance's role.
For customer managed KMS keys, key policies are the primary policy document and must permit access; IAM policies alone are insufficient.
2
Check the operational state of the KMS key.
Verify the key is not in a disabled, pending import, or pending deletion state.
KMS cryptographic actions require the key to be in the Enabled state to function.

Anahtar Kavram

Understanding KMS key policy precedence and key state lifecycle for cryptographic operations.
Soru 578Soru

A company runs large-scale, ad-hoc data processing jobs using Amazon EMR. The run schedule and scale of these jobs vary greatly based on client data delivery, leading to highly variable but legitimate compute costs. A SysOps administrator needs to implement a solution that detects unexpected cost spikes due to configuration errors or orphaned resources, while minimizing false alarms caused by the variable EMR workloads. Which solution meets these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Create an AWS Cost Anomaly Detection monitor using the AWS services monitor type, and create an alert subscription with an alerting threshold to notify the administrator of anomalies.

Cevap

Create an AWS Cost Anomaly Detection monitor using the AWS services monitor type, and create an alert subscription with an alerting threshold to notify the administrator of anomalies.
AWS Cost Anomaly Detection uses machine learning to dynamically baseline and monitor cost patterns for individual AWS services. This approach accommodates the highly variable and ad-hoc nature of workloads like Amazon EMR by adapting to historical spend trends, thereby minimizing false positives and alerting the administrator only when an actual anomaly is detected.

Adım Adım Çözüm

1
Identify the nature of the workload's cost pattern.
The workload has highly variable, ad-hoc, but legitimate cost spikes.
Understanding the cost pattern helps in selecting a tool that can adapt to variance without generating excessive false alerts.
2
Evaluate the capabilities of AWS billing and monitoring tools.
AWS Cost Anomaly Detection uses machine learning to automatically establish baselines and detect anomalous deviations, whereas AWS Budgets use static thresholds.
Machine learning-based anomaly detection is required to distinguish true anomalies from legitimate variable usage.
3
Configure the monitor and alert subscription.
Select the AWS services monitor type to evaluate Amazon EMR spend individually and set up an email or SNS alert subscription.
A service-level monitor evaluates cost anomalies per service, and the alert subscription ensures timely notification with minimal operational overhead.

Anahtar Kavram

AWS Cost Anomaly Detection for variable workloads
Tahmini Süre:1m 30s
Soru 579Soru

A SysOps administrator is troubleshooting internet connectivity issues for an Amazon EC2 instance in a private subnet with CIDR block 10.0.1.0/2410.0.1.0/24. The VPC contains a public subnet with CIDR block 10.0.0.0/2410.0.0.0/24. To save costs, the administrator deployed a custom EC2 NAT instance in the public subnet instead of a NAT Gateway.

The administrator has performed the following configuration steps:
- Configured the private subnet's route table with a route for 0.0.0.0/00.0.0.0/0 targeting the network interface (ENI) of the NAT instance.
- Configured the public subnet's route table with a route for 0.0.0.0/00.0.0.0/0 targeting the VPC's Internet Gateway.
- Enabled IP forwarding in the operating system of the NAT instance.
- Configured the security groups and Network ACLs to allow all traffic.

Despite these settings, the EC2 instance in the private subnet cannot reach any internet resources. Which of the following actions will resolve this connectivity issue?

Cevabı ve açıklamayı göster

Cevap: Disable the source/destination check attribute on the NAT instance's network interface.

Cevap

Disable the source/destination check attribute on the NAT instance's network interface.
By default, Amazon EC2 instances perform source/destination checking. This means the instance must be the source or destination of any traffic it sends or receives. Because a NAT instance acts as an intermediary, forwarding traffic where it is neither the original source nor the final destination, the Source/Destination Check attribute must be disabled on its network interface to allow forwarding of internet-bound traffic from the private subnet.

Adım Adım Çözüm

1
Analyze the packet path from the private instance to the internet.
The packet goes from the private instance to the private route table, which correctly redirects 0.0.0.0/00.0.0.0/0 traffic to the NAT instance's network interface (ENI).
Verifies that the route tables are configured to send internet traffic to the NAT intermediary.
2
Check the default AWS EC2 network interface attributes that affect traffic forwarding.
By default, AWS EC2 instances perform source/destination checking, which drops packets where the source or destination IP does not match the instance's own IP.
Since the NAT instance forwards traffic on behalf of the private instance, it will drop forwarded packets under default settings.
3
Disable the Source/Destination Check attribute on the NAT instance's elastic network interface (ENI).
The NAT instance is now permitted to accept, translate, and forward packets that did not originate from it.
This allows the operating system's IP forwarding configurations to route the packets successfully to the Internet Gateway.

Anahtar Kavram

Disabling Source/Destination Checking on NAT and Firewall Instances
Soru 580Soru

An organization's deployment contains an Application Load Balancer (ALB) that routes traffic to a fleet of Amazon EC2 instances. The application operates on port 50005000, and the target group is configured to use port 50005000 for routing. A dedicated health monitoring service runs on the instances on port 90009000, and the target group's health check port is explicitly configured to 90009000. All instances are currently marked as unhealthy with the status code `HealthCheck.Timeout`. The administrator reviews the security rules:

- The security group assigned to the ALB allows inbound HTTPS traffic on port 443443 from 0.0.0.0/00.0.0.0/0. Its outbound rules only allow TCP traffic on port 50005000 directed to the EC2 instances' security group.
- The security group assigned to the EC2 instances allows inbound TCP traffic on port 50005000 from the ALB security group. All outbound traffic is permitted.

Which two configuration changes are required to allow the health checks to pass? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Add an outbound rule to the ALB's security group to allow TCP traffic on port 90009000 to the security group of the EC2 instances.; Add an inbound rule to the security group of the EC2 instances to allow TCP traffic on port 90009000 from the security group of the ALB.

Cevap

To resolve the health check timeouts, both the outbound rules of the ALB's security group and the inbound rules of the EC2 instances' security group must be updated to permit TCP traffic on port 90009000.
The health checks are timing out because TCP port 90009000 traffic is blocked. Since the health check port is explicitly set to 90009000, the ALB must be permitted to send outbound traffic on port 90009000, and the EC2 instances must be permitted to accept inbound traffic on port 90009000. Adding the outbound rule to the ALB's security group and the inbound rule to the EC2 instances' security group establishes this connectivity.

Adım Adım Çözüm

1
Identify the port configured for target group health checks, which is port 90009000.
This establishes that the health check traffic travels from the ALB to the EC2 instances on TCP port 90009000.
Health checks must have a clear path on the designated port through all firewalls.
2
Review the outbound rules of the ALB's security group.
The current rule restricts outbound traffic to port 50005000. Update it to allow TCP traffic on port 90009000 to the security group of the EC2 instances.
This allows the ALB to send health check requests to the instances on port 90009000.
3
Review the inbound rules of the EC2 instances' security group.
The current rule only allows inbound traffic on port 50005000. Update it to allow TCP traffic on port 90009000 from the ALB security group.
This permits the EC2 instances to accept the health check traffic from the ALB.

Anahtar Kavram

Security groups are stateful firewalls; however, both the source (ALB) and destination (EC2) security groups must explicitly allow traffic on the health check port if the default 'allow all outbound' rule is restricted.
ÖncekiSayfa 29 / 49Sonraki
Tüm alıştırma soruları — AWS Certified SysOps Administrator - Associate | Examkin