Tüm alıştırma soruları

976 soru

Soru 41Soru

A SysOps Administrator is setting up VPC Flow Logs in Account A to publish network traffic metadata to an Amazon S3 bucket in Account B. The S3 bucket in Account B is configured with default encryption using a customer managed AWS KMS key. The flow logs are failing to deliver to the S3 bucket. Which of the following actions must be taken to successfully deliver the flow logs to the destination S3 bucket? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Modify the S3 bucket policy in Account B to allow the delivery.logs.amazonaws.com service principal to perform s3:PutObject and s3:GetBucketAcl actions.; Modify the customer managed KMS key policy in Account B to grant the delivery.logs.amazonaws.com service principal the kms:GenerateDataKey* permission.

Cevap

To deliver cross-account VPC Flow Logs to an S3 bucket encrypted with a customer managed KMS key, the administrator must modify the S3 bucket policy in Account B to allow delivery.logs.amazonaws.com to perform s3:PutObject and s3:GetBucketAcl, and modify the customer managed KMS key policy in Account B to allow delivery.logs.amazonaws.com to perform kms:GenerateDataKey*.
To publish cross-account VPC Flow Logs to an S3 bucket encrypted with a customer managed KMS key, two permissions must be configured. First, the S3 bucket policy in Account B must allow the delivery.logs.amazonaws.com service principal to write objects (s3:PutObject) and read the bucket ACL (s3:GetBucketAcl). Second, the KMS key policy of the customer managed key in Account B must grant the delivery.logs.amazonaws.com service principal the kms:GenerateDataKey* permission to allow encryption of the log files upon delivery.

Adım Adım Çözüm

1
Analyze the destination requirements for VPC Flow Logs publishing to S3.
Identify that VPC Flow Logs uses the log delivery service (delivery.logs.amazonaws.com) to write logs to S3 and does not use an IAM role.
This determines that configurations must be done using resource-based policies rather than creating client-side IAM roles.
2
Configure the bucket policy in Account B.
The bucket policy is updated to grant s3:PutObject and s3:GetBucketAcl to delivery.logs.amazonaws.com.
This grants the cross-account service permission to write the log files to the S3 bucket.
3
Address the S3 encryption requirement.
The customer managed KMS key policy is updated to grant kms:GenerateDataKey* to delivery.logs.amazonaws.com.
Because the S3 bucket uses customer managed KMS encryption, the log delivery service must be allowed to generate data keys to encrypt objects as it writes them.

Anahtar Kavram

Cross-account VPC Flow Logs delivery to an encrypted Amazon S3 bucket requires resource-based permissions (bucket policy and KMS key policy) for the Log Delivery service principal (delivery.logs.amazonaws.com), rather than user-configured IAM roles.
Soru 42Soru

A financial transaction application uses a Multi-AZ Amazon RDS for PostgreSQL DB instance. Following an unplanned failover event, logs indicate that the database successfully transitioned to the standby instance within 40 seconds. However, the application server pool was unable to reconnect to the database for over five minutes, resulting in dropped client requests. A SysOps Administrator discovers that the application servers continued resolving the RDS endpoint to the IP address of the failed primary instance.

Which combination of actions should the SysOps Administrator take to resolve this issue and minimize failover recovery time? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy Amazon RDS Proxy between the application servers and the database instance, and update the application to connect to the proxy endpoint.; Reduce the DNS caching Time to Live (TTL) value in the application server's Java Virtual Machine (JVM) configuration settings.

Cevap

Deploying Amazon RDS Proxy between the application and the database instance, and reducing the DNS caching Time to Live (TTL) value in the application server's JVM configuration settings.
Deploying Amazon RDS Proxy allows the application to remain connected to the proxy endpoint while the proxy handles the backend failover to the promoted standby instance transparently. Additionally, reducing the JVM DNS caching TTL forces the application servers to discard cached IP records and query DNS again, enabling them to discover the new CNAME target quickly.

Adım Adım Çözüm

1
Analyze failover behavior and DNS resolution caching.
The application server continues to connect to the cached IP address of the failed primary instance instead of performing a new DNS lookup for the updated CNAME.
Identify why the application server experienced a prolonged outage despite a successful database-level failover.
2
Configure the JVM DNS cache TTL.
The JVM DNS cache TTL is lowered (e.g., to 30 seconds), forcing the application server to query the DNS name server again shortly after the failover.
Ensure the application server resolves the new IP address of the promoted standby instance once the RDS CNAME record is updated.
3
Implement Amazon RDS Proxy.
Active application connections are preserved by the proxy during failover, and queries are automatically routed to the new primary database instance.
Provide connection pooling and abstract the failover process from the application layer to minimize client reconnection delays.

Anahtar Kavram

RDS Multi-AZ failovers update the CNAME record of the database endpoint. Applications must either bypass DNS lookup delays using a proxy (like Amazon RDS Proxy) or configure their client-side DNS caching (like JVM TTL) to expire stale records quickly.
Soru 43Soru

A SysOps Administrator is setting up a blue/green deployment for an Amazon ECS service using AWS CodeDeploy. The deployment must shift 10% of the traffic to the new version initially, wait 10 minutes, and then route the remaining 90% of the traffic to the new version. If the new version fails any health checks or triggers standard error rate alarms during the test period, the deployment must automatically roll back. Which TWO configuration steps should the administrator take to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Select the CodeDeployDefault.ECSCanary10Percent10Minutes deployment configuration in the deployment group settings.; Add CloudWatch alarms to the deployment group's rollback configuration to monitor for errors during the deployment.

Cevap

The SysOps Administrator should select the CodeDeployDefault.ECSCanary10Percent10Minutes deployment configuration in the deployment group settings, and add CloudWatch alarms to the deployment group's rollback configuration to monitor for errors during the deployment.
The correct strategy uses AWS CodeDeploy's native ECS integration. The preconfigured setting shifts a small portion of traffic (10%) to the replacement task set for a brief trial period (10 minutes) before completing the shift to 100%. To implement automatic rollback, CloudWatch alarms must be attached to the deployment group. If the alarms trigger during the deployment, CodeDeploy will roll back to the original task set.

Adım Adım Çözüm

1
Configure AWS CodeDeploy deployment group traffic shifting behavior.
The traffic routing is defined as a canary shift where 10% of traffic goes to the replacement task set first.
To meet the exact traffic shifting requirements without custom script development.
2
Configure CloudWatch alarm tracking within the CodeDeploy deployment group.
The deployment group will monitor specified metrics such as target response times or error rates.
To trigger automatic rollbacks without manual intervention if metrics degrade during the 10-minute testing phase.

Anahtar Kavram

AWS CodeDeploy integration with Amazon ECS for automated canary deployments and rollbacks.
Soru 44Soru

An organization uses AWS Config Conformance Packs to evaluate Amazon EBS volume encryption compliance across multiple AWS Regions. After deploying the conformance pack, a SysOps Administrator notices that for one specific region, the AWS Config rules show a compliance status of 'No data available' for all EBS volumes, even though several volumes are present in that region. The conformance pack deployment status itself is 'Completed' in the region.

Which two options would explain why the rules are not evaluating the EBS volumes? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: The AWS Config configuration recorder in the target region is not configured to record the AWS::EC2::Volume resource type.; The AWS Config configuration recorder is not started (active) in the target region.

Cevap

The correct answers are that the AWS Config configuration recorder in the target region is not configured to record the AWS::EC2::Volume resource type, and the configuration recorder is not started (active) in the target region.
The correct options represent the two fundamental requirements for AWS Config to perform rule evaluations on resources. First, the configuration recorder must be active (started) in the target region. Second, the configuration recorder must be configured to record the specific resource type being evaluated (in this case, EBS volumes, represented by AWS::EC2::Volume). If either requirement is not met, AWS Config will not generate configuration items for those resources, and the rules will show a compliance status of 'No data available'.

Adım Adım Çözüm

1
Analyze the symptom.
The conformance pack template successfully deployed ('Completed'), meaning the rules exist in the region, but they display 'No data available' for existing EBS volumes.
This isolates the issue from template syntax errors or deployment failures, pointing to rule evaluation execution issues.
2
Examine rule evaluation mechanics.
AWS Config rules require configuration items (CIs) captured by the configuration recorder to perform compliance evaluations.
Understanding that rules do not query resources directly; they rely on the recording history database generated by the configuration recorder.
3
Identify recording scope and state prerequisites.
If the configuration recorder is stopped or is not configured to record AWS::EC2::Volume resource types, no CIs will be generated for evaluations to run.
This establishes that both the running state of the recorder and the resource inclusion list are critical prerequisites for rule evaluation.
4
Evaluate the distractors.
Delivery channel configuration issues, missing EventBridge rules, and iam:PassRole permissions do not cause rule evaluation to result in 'No data available'.
This confirms that the other options represent different parts of the configuration lifecycle (delivery, automated remediation, event routing) and are not execution dependencies for Config rules.

Anahtar Kavram

AWS Config Rule Evaluation Prerequisites
Soru 45Soru

A company is designing a disaster recovery (DR) architecture for a critical web application. The application's database runs on an Amazon RDS for MySQL DB instance, and its static backup archives are stored in an Amazon S3 bucket. The SysOps administrator must configure the infrastructure to meet the following requirements:

1. The database must automatically fail over to a standby instance in a different Availability Zone during an outage, achieving a Recovery Time Objective (RTO) of under 2 minutes.
2. The S3 backup archives must be automatically replicated to a secondary AWS Region to protect against regional disasters, achieving a Recovery Point Objective (RPO) of 15 minutes.

Which combination of actions must the SysOps administrator perform to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Enable Multi-AZ deployment on the Amazon RDS for MySQL DB instance.; Enable bucket versioning on both the source S3 bucket and the destination S3 bucket, then configure Amazon S3 Cross-Region Replication (CRR) to the secondary Region.

Cevap

To meet the requirements, the administrator must enable Multi-AZ deployment on the Amazon RDS for MySQL DB instance, and enable bucket versioning on both the source and destination S3 buckets before configuring S3 Cross-Region Replication (CRR).
The correct options are enabling Multi-AZ deployment on the RDS instance and enabling bucket versioning on both S3 buckets before configuring Cross-Region Replication. RDS Multi-AZ provides synchronous replication and automatic failover to a standby instance in another Availability Zone, typically completed within 60 to 120 seconds, satisfying the strict recovery time requirement. Amazon S3 Cross-Region Replication automatically replicates new objects to a bucket in a different Region, but requires versioning to be enabled on both the source and destination buckets to track object versions.

Adım Adım Çözüm

1
Configure database high availability by modifying the Amazon RDS for MySQL DB instance.
Select the Multi-AZ deployment option to provision a synchronous standby DB instance in a different Availability Zone.
This ensures automatic failover and DNS redirection in the event of an infrastructure failure, meeting the RTO of under 2 minutes.
2
Prepare the source S3 bucket and a new destination S3 bucket in the secondary AWS Region.
Enable versioning on both S3 buckets.
Versioning is a strict requirement for S3 replication; replication cannot be enabled without it.
3
Establish S3 Cross-Region Replication (CRR) between the source and destination buckets.
Configure replication rules to copy all objects to the destination bucket in the secondary Region.
This satisfies the requirement to automatically replicate backup archives to another Region for disaster recovery.

Anahtar Kavram

Setting up high availability via RDS Multi-AZ and cross-region durability via S3 Cross-Region Replication, including prerequisite bucket versioning.
Soru 46Soru

A SysOps Administrator is setting up VPC Flow Logs to capture traffic from a critical production subnet and deliver the log events to an Amazon CloudWatch Logs log group. When trying to create the VPC Flow Log using an existing IAM role, the AWS Management Console displays an Access Denied error, despite the IAM role having a trust policy that allows the vpc-flow-logs.amazonaws.com service to assume it. Additionally, the administrator must ensure that these security logs do not incur indefinite storage costs.

Which of the following actions should the administrator take to resolve the creation error and manage the storage costs? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Attach an IAM policy to the administrator's user or group that grants the iam:PassRole permission for the VPC Flow Logs IAM role.; Configure the retention setting on the destination CloudWatch Logs log group to automatically expire logs after a defined duration.

Cevap

Attach an IAM policy to the administrator's user or group that grants the iam:PassRole permission for the VPC Flow Logs IAM role, and configure the retention setting on the destination CloudWatch Logs log group to automatically expire logs after a defined duration.
The correct options are to grant the iam:PassRole permission to the administrator's user policy, and to configure a retention period directly on the destination CloudWatch Logs log group. The iam:PassRole permission is required for the user/operator to associate an IAM role with the flow log configuration. Configuring retention on the destination CloudWatch Logs log group ensures that log events are automatically deleted after a specified period, optimizing cost.

Adım Adım Çözüm

1
Address the Access Denied issue by modifying the SysOps Administrator's IAM permissions.
Adding the iam:PassRole action to the administrator's IAM policy for the flow logs role allows the console to pass the role to the VPC Flow Logs service.
Creating a VPC Flow Log requires the creator to have permission to pass the IAM role that the service will assume.
2
Configure the retention settings on the CloudWatch Logs log group.
The log group is configured with a specific retention period (e.g., 90 days) instead of the default Never Expire setting.
This automatically purges older log data and controls long-term storage costs.

Anahtar Kavram

Configuring permissions and lifecycle options for VPC Flow Logs requires both identity-based permissions (iam:PassRole) to delegate the service role and log group retention policies in CloudWatch to optimize storage costs, as delivery itself occurs out-of-band.
Soru 47Soru

A SysOps administrator is configuring a VPC Flow Log to publish traffic metadata from a custom VPC to an Amazon CloudWatch Logs log group. The administrator has already created the target log group and an IAM role named VPCFlowLogRole that trusts the vpc-flow-logs.amazonaws.com service principal. The IAM role has a policy that allows it to create log streams and publish log events. When the administrator attempts to create the flow log, the operation fails with an authorization error. Additionally, company security policy requires that flow log data must not be stored indefinitely. Which combination of actions will resolve the creation error and meet the security requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Add iam:PassRole permissions to the IAM policy of the SysOps administrator, targeting the Amazon Resource Name (ARN) of the VPCFlowLogRole.; Configure a retention period on the CloudWatch Logs log group to automatically expire log events after the desired timeframe.

Cevap

To resolve the authorization issue and comply with the log retention policy, the SysOps administrator must have the iam:PassRole permission for the VPCFlowLogRole in their IAM policy, and a log retention period must be configured on the CloudWatch Logs log group destination.
The correct combination requires granting the SysOps administrator the iam:PassRole permission to pass the VPCFlowLogRole to the VPC Flow Logs service, which resolves the creation-time authorization error. Additionally, configuring the log retention period on the CloudWatch Logs log group ensures that log events are automatically deleted after the specified time and not stored indefinitely.

Adım Adım Çözüm

1
Analyze the cause of the authorization failure during VPC Flow Log creation.
The VPC Flow Logs service requires a service role (VPCFlowLogRole) to write logs to CloudWatch. When an administrator creates the flow log and associates it with this role, AWS checks if the administrator has permission to delegate (pass) that role. The missing permission is iam:PassRole on the administrator's policy.
Ensures the administrator has the administrative authority to assign the role to the AWS service.
2
Address the log retention security requirement.
Confirm that VPC Flow Logs configurations themselves do not support lifecycle or retention management. The logs are delivered to a CloudWatch Logs log group, which supports configurable retention periods (e.g., 30 days, 90 days, etc.) rather than the default 'Never Expire'.
Allows compliance with the organizational requirement to not store log data indefinitely while keeping configuration at the correct destination resource level.

Anahtar Kavram

VPC Flow Logs Permission Delegation and Destination Log Management
Soru 48Soru

A company recently configured consolidated billing using AWS Organizations and completed the migration of several workloads. To track spending across departments, a SysOps Administrator used AWS CloudFormation to provision all resources with the `CostCenter` and `BusinessUnit` tag keys. However, when trying to create a monthly cost report in AWS Cost Explorer, the administrator finds that these tag keys are not available as filtering options. Which of the following steps must the SysOps Administrator take to resolve this issue and make these tags available in AWS Cost Explorer? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Log in to the management account of the organization, open the Billing and Cost Management console, and activate the tag keys under Cost Allocation Tags.; Wait up to 24 hours after activation for the tag keys to become available as filters in AWS Cost Explorer.

Cevap

To resolve the issue, the administrator must log in to the management account of the organization, open the Billing and Cost Management console, and activate the tag keys under Cost Allocation Tags. Additionally, they must wait up to 24 hours for the activated tags to appear as filters in AWS Cost Explorer.
The correct answer requires performing tag activation from the management account because only the management (payer) account can enable user-defined cost allocation tags for consolidated billing. Furthermore, after activation, it takes up to 24 hours for AWS to update the metadata and populate the tag keys as filters in AWS Cost Explorer.

Adım Adım Çözüm

1
Access the AWS Billing and Cost Management console using the organization's management account credentials.
The administrator accesses the centralized billing console where cost allocation tags are managed for the entire organization.
Only the management account can activate cost allocation tags for consolidated billing in AWS Organizations.
2
Navigate to the Cost Allocation Tags section, select the 'CostCenter' and 'BusinessUnit' keys under User-defined cost allocation tags, and click Activate.
The selected tags are marked for activation in the billing system.
By default, user-defined tags applied to AWS resources are inactive for cost allocation and must be explicitly activated.
3
Allow up to 24 hours for the activation to process and the keys to appear in Cost Explorer.
The active tags become available as filtering and grouping options in AWS Cost Explorer.
There is a standard processing delay of up to 24 hours for cost allocation tag updates to propagate to the billing reporting tools.

Anahtar Kavram

Cost Allocation Tags require central activation in the Billing and Cost Management console of the management account, followed by a propagation period before they can be used in cost reports.
Soru 49Soru

An organization runs an application on Amazon EC2 instances in a private VPC subnet. The application frequently reads and writes data to an Amazon DynamoDB table. A SysOps Administrator notices a significant increase in NAT Gateway data processing charges. To eliminate these charges, the administrator deploys a Gateway VPC Endpoint for Amazon DynamoDB within the VPC. However, monitoring tools reveal that the EC2 instances are still routing all DynamoDB traffic through the NAT Gateway. Which of the following is the most likely cause of this behavior?

Cevabı ve açıklamayı göster

Cevap: The route table associated with the private subnet was not selected during the gateway endpoint configuration, preventing the DynamoDB prefix list route from being automatically added.

Cevap

The route table associated with the private subnet was not selected during the gateway endpoint configuration, preventing the DynamoDB prefix list route from being automatically added.
The correct option is that the private subnet's route table was not selected during the gateway endpoint configuration. Gateway VPC Endpoints function by automatically adding a route to the associated route tables. This route maps the prefix list of the destination service (e.g., DynamoDB) to the VPC endpoint ID. If the private subnet's route table is not selected during creation or update, the route is not added, and traffic continues to route through the default path (the NAT Gateway).

Adım Adım Çözüm

1
Identify the endpoint type required for Amazon DynamoDB.
DynamoDB uses a Gateway VPC Endpoint by default.
This determines how routing and network access controls are applied.
2
Analyze how Gateway VPC Endpoints modify routing.
They add a route mapping the DynamoDB prefix list (plxxxxxxpl-xxxxxx) to the gateway endpoint (vpcexxxxxxvpce-xxxxxx) in associated route tables.
Traffic to DynamoDB is routed at the subnet level rather than resolving to private IP addresses on interface endpoints.
3
Diagnose why traffic is still routed to the NAT Gateway.
If the private subnet's route table was not selected during endpoint creation, the prefix list route is missing from that route table.
Without the prefix list route, traffic default-routes to the NAT Gateway.

Anahtar Kavram

Gateway VPC Endpoints route traffic using subnet route tables and prefix lists, without utilizing Elastic Network Interfaces, security groups, or private DNS settings.
Soru 50Soru

A financial company is auditing its cloud expenditures across several member accounts within an AWS Organization. To track costs associated with a new data analysis project, a SysOps Administrator has written a Python script using AWS Systems Manager to apply a tag with the key `ProjectAnalysis` and value `DataLake` to all active Amazon EBS volumes. However, when the administrator logs into AWS Cost Explorer in the management account, the `ProjectAnalysis` tag is not available as a filtering option. Which action should the SysOps Administrator take to ensure the tag can be used to filter costs?

Cevabı ve açıklamayı göster

Cevap: Access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate.

Cevap

Access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate.
The correct answer is to access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate. In AWS Organizations with consolidated billing, user-defined cost allocation tags must be centrally activated by the management (payer) account. Once activated, AWS begins to track costs associated with these tags, allowing them to appear as filters in AWS Cost Explorer.

Adım Adım Çözüm

1
Sign in to the AWS Management Console using the credentials for the management (payer) account of the AWS Organization.
Access is granted to organization-wide billing configurations.
Only the management account has the authority to activate cost allocation tags for consolidated billing across all linked member accounts.
2
Navigate to the AWS Billing and Cost Management console, select 'Cost Allocation Tags' from the navigation pane, locate the user-defined tag key `ProjectAnalysis`, select it, and click 'Activate'.
The tag is marked as active for cost allocation.
User-defined tags applied to AWS resources do not automatically function as cost allocation tags. They must be manually activated to begin appearing in billing reports and Cost Explorer.
3
Wait for the active tag to propagate to Cost Explorer, which typically takes up to 24 hours.
The `ProjectAnalysis` tag becomes available as a filter and grouping category in Cost Explorer.
Activation triggers AWS to begin tracking the cost data for resources bearing that tag key from that point forward.

Anahtar Kavram

Activation of Cost Allocation Tags in AWS Organizations
Soru 51Soru

An organization runs an API service on AWS Fargate tasks registered to an Application Load Balancer (ALB) target group using the 'ip' target type. The API receives client requests over HTTPS on port 8443, but the backend application container exposes an HTTP endpoint on port 8080 specifically for health status monitoring. The SysOps Administrator notices that the target group shows all Fargate tasks as unhealthy with the description 'Health checks failed with a connection timeout'. Which two actions should the administrator take to resolve this health check issue? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Modify the target group settings to specify port 8080 as the health check port.; Update the ECS Fargate tasks' security group to allow inbound traffic on port 8080 from the Application Load Balancer's security group.

Cevap

Modify the target group settings to specify port 8080 as the health check port, and update the ECS Fargate tasks' security group to allow inbound traffic on port 8080 from the Application Load Balancer's security group.
The correct configuration requires overriding the target group's default health check port to port 8080 since that is where the backend application is listening for health status probes. In addition, the security group of the ECS Fargate tasks must permit inbound traffic on port 8080 from the Application Load Balancer's security group to allow the health check probes to pass through.

Adım Adım Çözüm

1
Analyze the reported error message.
The target group reports 'Health checks failed with a connection timeout', indicating that the ALB cannot establish a network connection to the targets on the designated health check port.
Identifying the root cause requires recognizing that connection timeouts are network or firewall-related, rather than application response errors (like 4xx/5xx codes).
2
Check port configuration alignment.
The API receives client traffic on port 8443, but the health monitoring endpoint runs on port 8080. The target group must be explicitly configured to override the traffic port for health checks and use port 8080 instead.
By default, target groups send health probes to the same port configured for traffic. If the health check endpoint is on a different port, it must be overridden.
3
Check security group ingress rules.
The Fargate tasks' security group needs to permit inbound traffic on port 8080 from the security group of the ALB.
Even if the target group is correctly configured, the Fargate container firewall will drop health check packets on port 8080 if the ingress rules do not explicitly permit it.

Anahtar Kavram

ELB Target Group Health Check Port Overrides and Target Security Group Configurations
Soru 52Soru

A SysOps Administrator is configuring Amazon EC2 instances in a private subnet with no internet access to be managed by AWS Systems Manager Session Manager. The Administrator creates the required Interface VPC Endpoints for the `ssm`, `ssmmessages`, and `ec2messages` services within the VPC. The security group for the Interface VPC Endpoints is configured to allow inbound HTTPS traffic from the EC2 instances. However, the SSM Agent on the EC2 instances fails to connect to the Systems Manager service.

Which of the following is the most likely cause of this issue?

Cevabı ve açıklamayı göster

Cevap: Private DNS hostnames are disabled for the Interface VPC Endpoints, causing the SSM Agent to attempt to resolve the default public Systems Manager endpoints instead of the private endpoints.

Cevap

Private DNS hostnames are disabled for the Interface VPC Endpoints, causing the SSM Agent to attempt to resolve the default public Systems Manager endpoints instead of the private endpoints.
Enabling Private DNS hostnames allows the default public service endpoints to resolve to the private IP addresses of the Interface VPC Endpoint's Elastic Network Interfaces (ENIs). Since the EC2 instances do not have internet access, they cannot reach the public IPs of the service endpoints. Enabling Private DNS ensures the connection remains internal and secure.

Adım Adım Çözüm

1
Analyze the connection requirements for the Systems Manager (SSM) Agent.
The SSM Agent needs to connect to the Systems Manager service endpoints (ssm, ssmmessages, ec2messages).
To establish a Session Manager session, the SSM Agent on the EC2 instances must communicate with these endpoints.
2
Evaluate why the connection fails despite correct security groups and lack of internet access.
Without Private DNS hostnames enabled, the agent attempts to resolve the standard public endpoints (e.g., ssm.us-east-1.amazonaws.com) which resolve to public IP addresses.
Since the private subnet has no internet access, attempts to connect to public IP addresses will time out.
3
Determine the correct configuration to force private routing.
Enable Private DNS hostnames on the Interface VPC Endpoints.
This automatically overrides the public DNS names to resolve to the private IPs of the endpoint's elastic network interfaces within the VPC.

Anahtar Kavram

VPC Endpoints and PrivateLink Integration
Soru 53Soru

A company has deployed a TCP-based application on a fleet of Amazon EC2 instances in a private subnet. The instances are registered as targets in a target group for an internet-facing Network Load Balancer (NLB) using the 'instance' target type. The application listens on port 9000, and the target group is configured with TCP health checks on port 9000. The NLB has client IP preservation enabled. A SysOps Administrator observes that all EC2 instances are marked as unhealthy in the target group, and clients are unable to connect to the application. Which two configurations must the SysOps Administrator verify or apply to resolve this issue? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: The security group associated with the EC2 instances allows inbound TCP traffic on port 9000 from the client IP ranges.; The security group associated with the EC2 instances allows inbound TCP traffic on port 9000 from the private IP addresses of the load balancer nodes.

Cevap

The correct configurations are to configure the security group associated with the EC2 instances to allow inbound TCP traffic on port 9000 from the client IP ranges, and to allow inbound TCP traffic on port 9000 from the private IP addresses of the Network Load Balancer nodes.
To resolve the issue, the security group associated with the EC2 instances must be configured to permit inbound traffic on the service port from both the clients and the load balancer. Because client IP preservation is enabled on the Network Load Balancer (NLB) for target groups of type 'instance', the source IP addresses of the client traffic are preserved. Therefore, the target EC2 instances receive requests with the clients' public IP addresses as the source, meaning the security group must allow inbound traffic from the client IP ranges. Concurrently, NLB health checks originate from the private IP addresses of the load balancer nodes. To make the targets healthy, the security group must also allow inbound TCP traffic on port 9000 from the load balancer's private IP addresses.

Adım Adım Çözüm

1
Analyze the load balancer type and target registration type.
The architecture uses an internet-facing Network Load Balancer (NLB) with targets registered by 'instance' target type and client IP preservation enabled.
Understanding the load balancer and registration type dictates how source IP addresses are handled at the target level.
2
Determine the source IP for client traffic reaching the targets.
Since client IP preservation is enabled and targets are registered by instance ID, the source IP of client traffic is the client's actual public IP address.
This determines that the target's security group must permit inbound traffic from the client IP ranges rather than the load balancer.
3
Determine the source IP for load balancer health check traffic reaching the targets.
NLB health check requests always originate from the private IP addresses of the load balancer nodes.
This determines that the target's security group must permit inbound traffic from the private IP addresses of the load balancer nodes (or the VPC CIDR) for health checks to succeed.
4
Select the two configuration adjustments required to allow traffic flow.
Adjust the EC2 security group to allow inbound port 9000 traffic from the clients (for application traffic) and from the NLB node private IPs (for health checks).
Both configurations are required: passing health checks makes targets healthy, and permitting client IPs allows actual traffic routing.

Anahtar Kavram

Network Load Balancer client IP preservation and health check source IP routing requirements.
Soru 54Soru

A SysOps Administrator is configuring automated monthly patching for a fleet of Amazon EC2 instances running Red Hat Enterprise Linux (RHEL). The administrator creates a custom patch baseline named RHEL-Critical-Baseline to approve only critical security updates. The target EC2 instances are tagged with the tag key Patch Group and the value RHEL-Production. The SSM Agent is running on all target instances, and an IAM instance profile with the AmazonSSMManagedInstanceCore policy is attached to all of them. The administrator then configures a Systems Manager State Manager association to run the AWS-RunPatchBaseline document on the instances tagged with Patch Group: RHEL-Production. During execution, the administrator observes that the instances are being patched, but they are receiving all updates from the default AWS-provided RHEL patch baseline rather than the custom RHEL-Critical-Baseline. Which action will resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Register the RHEL-Production patch group with the RHEL-Critical-Baseline custom patch baseline.

Cevap

Register the RHEL-Production patch group with the RHEL-Critical-Baseline custom patch baseline.
To apply a custom patch baseline, the associated patch group must be explicitly registered with it. If a patch group is not registered with any custom baseline, AWS Systems Manager Patch Manager automatically applies the default baseline for that operating system. Registering the RHEL-Production patch group with the RHEL-Critical-Baseline custom patch baseline ensures that instances in that patch group are evaluated against the custom baseline.

Adım Adım Çözüm

1
Inspect the managed nodes configuration and confirm that the target instances are successfully tagged with the Patch Group tag.
Confirming that the instances have Patch Group = RHEL-Production.
This confirms that Systems Manager can read the correct patch group metadata from the target nodes.
2
Verify if the patch group RHEL-Production has been registered to the custom patch baseline RHEL-Critical-Baseline in Patch Manager.
Identify that the patch group has not been registered to the custom baseline, causing Patch Manager to default to the AWS-provided default RHEL baseline.
By default, Patch Manager evaluates managed nodes against the default patch baseline unless their patch group is registered to a custom baseline.
3
Navigate to Systems Manager Patch Manager, select the RHEL-Critical-Baseline, and register the RHEL-Production patch group to it.
The association between the patch group and the custom patch baseline is established.
This registration overrides the default baseline behavior, ensuring the custom baseline is applied to all instances in this patch group during the next association run.

Anahtar Kavram

AWS Systems Manager Patch Groups and Baselines registration
Soru 55Soru

A SysOps administrator has configured an Amazon CloudWatch alarm to monitor the CPU utilization of an Auto Scaling group. The alarm is configured to send notifications to an Amazon SNS topic when the CPU utilization exceeds 80%80\%. The SNS topic is encrypted using a customer managed AWS KMS key. During a load test, the CPU utilization exceeded the threshold, and the alarm state changed to ALARM, but no notifications were sent.

Which TWO actions should the administrator take to resolve this issue? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Modify the AWS KMS key policy to grant the Amazon CloudWatch service principal (cloudwatch.amazonaws.com) permissions to execute the kms:Decrypt and kms:GenerateDataKey actions.; Modify the Amazon SNS topic access policy to grant the Amazon CloudWatch service principal (cloudwatch.amazonaws.com) permissions to execute the sns:Publish action.

Cevap

The administrator must modify the AWS KMS key policy to allow the CloudWatch service principal to perform the kms:Decrypt and kms:GenerateDataKey actions, and modify the Amazon SNS topic access policy to allow the CloudWatch service principal to perform the sns:Publish action.
To resolve the notification failure, the CloudWatch service principal must be granted explicit permissions on both the target resource and its encryption key. The configuration requires modifying the KMS key policy to permit the CloudWatch service principal (`cloudwatch.amazonaws.com`) to execute both `kms:Decrypt` and `kms:GenerateDataKey`. Additionally, the SNS topic access policy must grant `sns:Publish` access to `cloudwatch.amazonaws.com` so CloudWatch can deliver the alert messages.

Adım Adım Çözüm

1
Analyze the event flow and identify the failure point.
The CloudWatch alarm successfully changes state to ALARM, but the notification action fails because the target SNS topic is encrypted with a customer managed KMS key.
Since the alarm transitions but no message is sent, the issue lies in the authorization pathway between CloudWatch, SNS, and KMS.
2
Update the SNS topic access policy.
The CloudWatch service principal is granted sns:Publish permissions directly on the SNS topic.
By default, SNS topics do not allow external service principals like CloudWatch to publish messages unless explicitly defined in the access policy.
3
Update the customer managed KMS key policy.
The CloudWatch service principal is granted kms:Decrypt and kms:GenerateDataKey permissions on the KMS key used by the SNS topic.
When SNS topic encryption is enabled with a customer managed key, the publishing service (CloudWatch) must be allowed to use that key to encrypt the payload before delivery.

Anahtar Kavram

Permissions required for Amazon CloudWatch to publish to encrypted Amazon SNS topics
Soru 56Soru

A SysOps administrator is configuring a Python script hosted on an Amazon EC2 instance in Account A (111111111111111111111111) to automate the provisioning of temporary worker instances. The script uses the AWS SDK to call the `RunInstances` API and associates the new instances with an IAM instance profile that contains an IAM role named `WorkerExecutionRole`.

The EC2 instance running the script is associated with an IAM role named `AutomationAdminRole` which has the following IAM policy attached:

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:RunInstances",
"ec2:DescribeInstances"
],
"Resource": "*"
}
]
}

When the script execution is triggered, it fails with an `UnauthorizedOperation` error during instance launch.

Which modification to the IAM configuration of `AutomationAdminRole` is required to resolve this error?

Cevabı ve açıklamayı göster

Cevap: Add a statement to the IAM policy of AutomationAdminRole that allows the iam:PassRole action on the WorkerExecutionRole resource.

Cevap

Add a statement to the IAM policy of AutomationAdminRole that allows the iam:PassRole action on the WorkerExecutionRole resource.
The correct action is to add the iam:PassRole permission to the policy of the calling role (AutomationAdminRole) targeting the IAM role resource (WorkerExecutionRole). This allows the script running under AutomationAdminRole to associate WorkerExecutionRole with the new EC2 instances during the RunInstances API call.

Adım Adım Çözüm

1
Analyze the IAM identities involved in the script execution.
The script runs under the AutomationAdminRole identity and attempts to associate a new EC2 instance with the WorkerExecutionRole.
Identifying the active identity and the target role resource determines where the permission must be applied.
2
Identify the root cause of the provisioning error.
The script attempts to pass the WorkerExecutionRole to the EC2 service during the RunInstances call, which requires the iam:PassRole permission.
AWS requires explicit permission to pass an IAM role to an AWS service to prevent unauthorized privilege escalation.
3
Update the execution role's permissions policy.
Modify the policy attached to AutomationAdminRole to include the iam:PassRole action targeting the WorkerExecutionRole's Amazon Resource Name (ARN).
This satisfies the authorization check performed when the RunInstances call attempts to assign the role.

Anahtar Kavram

Using iam:PassRole to delegate permissions to AWS resources via service roles and instance profiles.
Soru 57Soru

A SysOps administrator is configuring a third-party monitoring application running on Amazon EC2 instances in a Shared Services account (333333333333333333333333). The application needs to analyze logs stored in an Amazon S3 bucket within a Production account (444444444444444444444444). The S3 bucket is encrypted with an AWS KMS Customer Managed Key (CMK) in the Production account. The application runs under an IAM instance profile associated with a role named `EC2MonitorRole` in the Shared Services account, and it must assume an IAM role named `CrossAccountReaderRole` in the Production account to read the S3 objects. Which of the following configuration steps are required to establish this cross-account access? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Modify the trust policy of the `CrossAccountReaderRole` in the Production account (444444444444444444444444) to allow the `sts:AssumeRole` action for the `arn:aws:iam::333333333333:role/EC2MonitorRole` principal.; Attach a permissions policy to the `EC2MonitorRole` in the Shared Services account (333333333333333333333333) that allows the `sts:AssumeRole` action on `arn:aws:iam::444444444444:role/CrossAccountReaderRole`.

Cevap

Modify the trust policy of the target role in the Production account to trust the source role, and attach an IAM policy to the source role allowing it to assume the target role.
Establishing cross-account access requires configuring permissions on both sides of the trust boundary. First, the source role must have permissions to initiate the assume-role request. Second, the target role's trust policy must list the source role as a trusted principal to allow the request.

Adım Adım Çözüm

1
Determine the delegation mechanism for cross-account access.
The EC2 instance profile's role (EC2MonitorRole) in the Shared Services account must call AWS STS to assume the target role (CrossAccountReaderRole) in the Production account.
This establishes a security boundary where temporary credentials are used to access the destination account's resources.
2
Configure the trust relationship on the target role.
The target role (CrossAccountReaderRole) trusts the source role (EC2MonitorRole) as a principal for the sts:AssumeRole action.
The target account must explicitly authorize which external entities are allowed to assume its roles.
3
Configure permissions on the source role.
The source role (EC2MonitorRole) is granted permission to perform sts:AssumeRole on the target role's ARN.
The source account's IAM policies must allow the identity to make the outbound sts:AssumeRole API call.

Anahtar Kavram

Cross-account trust delegation using IAM roles and AWS STS.
Soru 58Soru

A SysOps Administrator is setting up automated OS patching for a fleet of Amazon EC2 instances running Ubuntu 22.04 LTS. The organization requires a custom patch baseline that automatically approves security updates with a 'Critical' or 'Important' severity 10 days after release. Patching must occur during a weekly maintenance window, and target instances must be grouped dynamically. Arrange the steps in the correct chronological order to configure this automated patch management workflow, starting with the baseline configuration.

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

Cevabı ve açıklamayı göster

Cevap

To configure the automated patch management workflow: 1. Create a custom patch baseline for Ubuntu with the specified rules. 2. Tag the target EC2 instances with the case-sensitive tag key 'Patch Group'. 3. Associate the patch group with the custom patch baseline. 4. Create a Systems Manager Maintenance Window. 5. Register the target instances with the Maintenance Window. 6. Register the 'AWS-RunPatchBaseline' Run Command task with the Maintenance Window.
To automate patching with a custom baseline, the baseline must first be created with the required approval rules. Instances must then be tagged with the case-sensitive 'Patch Group' tag key to define the patch group. Next, the patch group is associated with the custom patch baseline. Then, a maintenance window is created to define the execution schedule. The target instances are registered with the maintenance window, and finally, the task executing the AWS-RunPatchBaseline document with the Install operation is registered to target those instances within the maintenance window.

Adım Adım Çözüm

1
Create the custom patch baseline with the specified OS, approval rules, and auto-approval delay.
A custom patch baseline is created but not yet applied to any instances.
You must define the patching rules (e.g., auto-approving Critical patches after 10 days) first before applying them.
2
Apply the 'Patch Group' tag key (case-sensitive) with a custom value (e.g., 'Prod-Ubuntu') to the target instances.
The target instances are logically grouped under the 'Prod-Ubuntu' patch group.
SSM Patch Manager uses the 'Patch Group' tag key to map instances to specific baselines.
3
Associate the patch group name with the custom patch baseline.
Instances tagged with the patch group are now bound to the custom patch baseline instead of the default one.
This association ensures SSM Patch Manager applies the custom rules to the correct group of instances.
4
Create a Systems Manager Maintenance Window specifying the schedule (e.g., weekly) and duration.
A maintenance window is established but has no targets or tasks associated with it.
The maintenance window provides the scheduling framework for running the patching task.
5
Register the target instances with the Maintenance Window using resource tags.
The Maintenance Window now has defined targets to run tasks against.
You must register targets to the window so the task knows which instances to execute on.
6
Register the 'AWS-RunPatchBaseline' Run Command task with the Maintenance Window, specifying the registered targets and the 'Install' operation.
The configuration is complete, and patching will execute automatically on the schedule.
The task definition links the actual patch execution command ('AWS-RunPatchBaseline') to the maintenance window schedule and registered targets.

Anahtar Kavram

AWS Systems Manager Patch Manager configuration workflow involving custom baselines, case-sensitive patch groups, and maintenance window scheduling.
Tahmini Süre:2m 30s
Soru 59Soru

A company is using AWS Config to monitor security compliance. A SysOps administrator needs to automate the remediation of publicly accessible Amazon Redshift clusters. The administrator has verified that the AWS Config rule redshift-cluster-public-access-check is active. An AWS Systems Manager Automation document named AWS-RevokeRedshiftClusterPublicAccess will be used to remediate non-compliant clusters.

Which two configuration actions must the SysOps administrator perform to establish this automated remediation pipeline? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create an Amazon EventBridge rule that triggers when an AWS Config Rules compliance change event has a complianceType of NON_COMPLIANT for the redshift-cluster-public-access-check rule.; Configure the Systems Manager Automation document as the target for the EventBridge rule, specifying an IAM role that grants EventBridge permission to start the automation.

Cevap

Create an EventBridge rule that triggers on AWS Config non-compliant compliance change events, and target the Systems Manager Automation document using an IAM role that grants EventBridge permission to execute the automation.
To automate compliance remediation, an Amazon EventBridge rule must be configured to capture compliance status changes from AWS Config. When the Config rule for Redshift public access evaluates a resource as non-compliant, it generates a 'Config Rules Compliance Change' event with a complianceType of NON_COMPLIANT. The EventBridge rule matches this event pattern. The target of this EventBridge rule must be the Systems Manager Automation document. To invoke this target, EventBridge requires an IAM service role with permission to execute the automation document, which is specified when setting up the target.

Adım Adım Çözüm

1
Define an Amazon EventBridge rule pattern that filters for 'Config Rules Compliance Change' events originating from the source 'aws.config'.
The rule will capture compliance state transitions for the redshift-cluster-public-access-check rule.
This ensures the remediation workflow is only initiated when a Redshift cluster is evaluated as NON_COMPLIANT.
2
Configure the rule's event pattern to match only compliance updates where detail.newEvaluationResult.complianceType is set to NON_COMPLIANT.
The EventBridge rule will ignore COMPLIANT state updates and only execute for non-compliant resources.
This prevents unnecessary executions of the remediation automation.
3
Set the target of the EventBridge rule to the Systems Manager Automation document AWS-RevokeRedshiftClusterPublicAccess, and select or create an IAM role for the target that allows ssm:StartAutomationExecution.
EventBridge will have the required permission to invoke the Automation document on the non-compliant resource.
By default, AWS services cannot access resources in your account without an IAM role granting explicit execution permissions.

Anahtar Kavram

Event-driven remediation using AWS Config compliance events, Amazon EventBridge rules, and AWS Systems Manager Automation.
Soru 60Soru

A SysOps Administrator is troubleshooting a failed stack update in AWS CloudFormation. The stack was created using a custom IAM service role named `CFNServiceRole` to restrict resource management permissions. During a recent update, a deployment error occurred, and the stack's status transitioned to `UPDATE_ROLLBACK_FAILED`. The administrator attempts to resume the rollback process using the AWS CLI, but receives an `AccessDenied` error when executing the command.

Which combination of actions is required to successfully resume and complete the rollback of the stack? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Attach an IAM policy to the administrator's IAM identity that grants the `iam:PassRole` permission for the `CFNServiceRole` ARN.; Run the `aws cloudformation continue-update-rollback` command specifying the stack name.

Cevap

To successfully resume and complete the rollback, the administrator must attach an IAM policy granting the `iam:PassRole` permission for the `CFNServiceRole` ARN to their own IAM identity, and then run the `aws cloudformation continue-update-rollback` command specifying the stack name.
The correct options are attaching an IAM policy with the `iam:PassRole` permission for the `CFNServiceRole` and running the `aws cloudformation continue-update-rollback` command. The `iam:PassRole` permission is required because CloudFormation uses the execution role to perform operations, and the user must be authorized to pass this role to the service. The `continue-update-rollback` command is the designated API action to resume a stack rollback that has entered the `UPDATE_ROLLBACK_FAILED` status.

Adım Adım Çözüm

1
Analyze the `AccessDenied` error during the rollback continuation attempt.
Identify that the CloudFormation stack utilizes a custom service role (`CFNServiceRole`) and the calling administrator identity lacks the privilege to pass this role to the CloudFormation service.
When a custom execution role is associated with a stack, any user performing operations on that stack must have permissions to pass that role.
2
Modify the administrator's IAM policy.
Attach a policy granting the `iam:PassRole` action targeting the ARN of `CFNServiceRole`.
This allows the administrator's identity to delegate the permissions of the service role to AWS CloudFormation for execution.
3
Invoke the rollback resume command.
Execute `aws cloudformation continue-update-rollback --stack-name <stack-name>`.
This command directs CloudFormation to attempt the rollback process again from the point where it failed, using the restored delegation permissions.

Anahtar Kavram

AWS CloudFormation Rollback Troubleshooting and IAM Service Roles
ÖncekiSayfa 3 / 49Sonraki