Tüm alıştırma soruları

976 soru

Soru 641Soru

A SysOps Administrator is setting up Same-Region Replication (SRR) between two Amazon S3 buckets within the same AWS account using the AWS CLI. The administrator has successfully enabled bucket versioning on both the source and destination S3 buckets. Additionally, they created an IAM service role named S3ReplicationServiceRole with a trust policy allowing the s3.amazonaws.com service principal to assume the role. The role's permissions policy grants all necessary S3 permissions to access the source bucket and write replicas to the destination bucket.

When the administrator attempts to apply the replication configuration using the command:

aws s3api put-bucket-replication --bucket source-bucket --replication-configuration file://replication.json

the command fails with an AccessDenied error. The administrator is currently logged in with an IAM user account that has the AWS managed AmazonS3FullAccess policy attached, but no other IAM permissions. Which modification is required to resolve this error and successfully apply the replication configuration?

Cevabı ve açıklamayı göster

Cevap: Add the iam:PassRole permission for the S3ReplicationServiceRole to the administrator's IAM user policy.

Cevap

Add the iam:PassRole permission for the S3ReplicationServiceRole to the administrator's IAM user policy.
To configure S3 replication, the IAM entity (user or role) executing the configuration API call must have the iam:PassRole permission for the replication role. This allows the user to delegate the role to S3. Even with AmazonS3FullAccess, the user cannot pass the IAM role without this specific permission, resulting in an AccessDenied error.

Adım Adım Çözüm

1
Analyze the IAM configuration context and the AccessDenied error.
The command fails when associating the IAM role with the bucket replication configuration, despite the user having full S3 permissions.
AWS services require a user to have the iam:PassRole permission to pass an IAM role to the service, which is checked during configuration association.
2
Verify S3 replication prerequisite states.
Versioning is enabled on both source and destination buckets, and the IAM replication role is correctly configured to trust the S3 service principal.
This rules out basic configuration issues like versioning omission or incorrect service trust relationships.
3
Formulate the required permission update for the administrator's user policy.
Add an inline or customer-managed policy to the user allowing the iam:PassRole action with the resource pointing to the replication role's ARN.
This authorizes the administrator to delegate the role to Amazon S3, allowing the CLI command to succeed.

Anahtar Kavram

IAM PassRole requirement for AWS service role delegation
Soru 642Soru

An organization uses AWS Service Catalog to distribute standardized infrastructure templates. The central hub account shares a portfolio with several spoke accounts. In one of the spoke accounts, the SysOps administrator creates a local launch constraint for a product in the shared portfolio. This launch constraint specifies a local IAM role named CustomProvisioningRole that possesses all necessary permissions to create the required resources. When a developer in the spoke account tries to launch the product, the deployment immediately fails, and the developer receives an error indicating that they do not have permission to perform the action. Which action must the administrator take to resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Attach an IAM policy to the developer's IAM identity in the spoke account that grants the iam:PassRole permission for the CustomProvisioningRole.

Cevap

Attach an IAM policy to the developer's IAM identity in the spoke account that grants the iam:PassRole permission for the CustomProvisioningRole.
To use a launch constraint, the user or role launching the product must have the iam:PassRole permission for the role specified in the constraint. This permission allows the user to pass the role to AWS Service Catalog, which then assumes the role to provision resources on behalf of the user.

Adım Adım Çözüm

1
Identify the authorization mechanism used for provisioning permissions during the AWS Service Catalog product launch.
The deployment uses a launch constraint pointing to a local IAM role named CustomProvisioningRole in the spoke account.
Understanding which principal initiates the resource creation and how permissions are delegated is key to diagnosing the authorization failure.
2
Analyze the error context where the developer fails to launch the product despite the local role having proper resource creation permissions.
The developer is the initiator who needs to pass the CustomProvisioningRole to the AWS Service Catalog service so the service can assume it.
AWS IAM requires explicit iam:PassRole permission on the user or group initiating a service call that involves passing an IAM role.
3
Formulate the correct policy change required on the developer's IAM identity in the spoke account.
Create and attach an IAM policy to the developer granting the iam:PassRole action on the CustomProvisioningRole resource.
This grants the developer the necessary authority to delegate the CustomProvisioningRole to the Service Catalog service.

Anahtar Kavram

AWS Service Catalog Launch Constraints and IAM Role Delegation
Soru 643Soru

An organization hosting a web application on AWS uses an Amazon EC2 Auto Scaling group (ASG). A SysOps administrator is configuring a scale-in lifecycle hook to back up application logs to an Amazon S3 bucket before any instance is terminated. A target tracking policy has just triggered a scale-in event.

Order the steps to show the sequence of events that occurs when an instance is terminated using this lifecycle hook, from the start of the scale-in process to the final termination.

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence begins when the Auto Scaling group selects the instance and transitions it to the Terminating:Wait state. Next, an EventBridge rule detects this transition and triggers the Systems Manager Run Command script. The script runs on the instance and uploads the logs to Amazon S3. Once complete, the script invokes the CompleteLifecycleAction API with the CONTINUE result, which allows the Auto Scaling group to transition the instance to Terminating:Proceed and terminate the instance.
The correct order follows the logical flow of the Amazon EC2 Auto Scaling scale-in lifecycle hook. First, the ASG identifies the instance to terminate and pauses termination by putting the instance into the 'Terminating:Wait' state. This state transition generates an EventBridge event, which triggers the Systems Manager Run Command. The Run Command script then executes on the instance to back up the logs to Amazon S3. Once the backup is complete, the script calls the CompleteLifecycleAction API with a CONTINUE result. Finally, the ASG transitions the instance to 'Terminating:Proceed' and terminates the instance.

Adım Adım Çözüm

1
Identify the initial event that pauses the scale-in process.
The Auto Scaling group selects the instance and transitions it to the Terminating:Wait state.
Lifecycle hooks intercept termination to run custom tasks, starting with placing the instance in a wait state.
2
Determine how the backup orchestration is triggered.
Amazon EventBridge detects the Terminating:Wait transition and triggers Systems Manager Run Command.
EventBridge rules are used to capture lifecycle state changes and trigger automation targets.
3
Perform the custom log backup task on the instance.
The Systems Manager Run Command script successfully uploads the application logs to the S3 bucket.
The instance must remain running in the wait state while the files are being transferred.
4
Signal completion to the Auto Scaling group.
The script invokes the CompleteLifecycleAction API call with the CONTINUE result.
An explicit API call is required to tell the ASG that the custom action has finished and it can proceed.
5
Complete the lifecycle transition and terminate the instance.
The Auto Scaling group transitions the instance to Terminating:Proceed and terminates the EC2 instance.
Receiving the CONTINUE result allows the Auto Scaling group to resume and complete the termination workflow.

Anahtar Kavram

Auto Scaling lifecycle hooks suspend instance state changes, allowing custom workflows (such as log archiving via Systems Manager and EventBridge) to execute before the instance proceeds to the next state.
Tahmini Süre:2m 0s
Soru 644Soru

A company runs a critical database on Amazon EC2 instances with Amazon EBS volumes in the us-east-1 Region. To meet a low Recovery Time Objective (RTO) during disaster recovery drills, a SysOps Administrator enables Fast Snapshot Restore (FSR) on the EBS snapshots in us-east-1. The EBS snapshots are copied to the us-west-2 Region daily using an AWS Backup plan. During a disaster recovery drill in us-west-2, the administrator restores an EBS volume from the copied snapshot into the us-west-2a Availability Zone. However, the database experiences high initial I/O latency, and the restored volume does not perform at its provisioned limit immediately.

Which of the following is the most likely cause of this performance degradation?

Cevabı ve açıklamayı göster

Cevap: Fast Snapshot Restore (FSR) is not automatically enabled on copied snapshots, and it must be explicitly enabled for the copied snapshot in the destination Region and target Availability Zone.

Cevap

Fast Snapshot Restore (FSR) is not automatically enabled on copied snapshots, and it must be explicitly enabled for the copied snapshot in the destination Region and target Availability Zone.
The correct answer is that Fast Snapshot Restore (FSR) is not automatically enabled on copied snapshots, and it must be explicitly enabled for the copied snapshot in the destination Region and target Availability Zone. When an EBS snapshot is copied across Regions, it acts as a standard snapshot in the destination Region. FSR must be explicitly enabled on the copied snapshot for the specific Availability Zones where the volumes will be restored. This ensures that the restored EBS volume has its blocks pre-warmed, avoiding the lazy-loading latency associated with pulling block data from Amazon S3 upon first access.

Adım Adım Çözüm

1
Analyze the behavior of EBS snapshots restored in a secondary Region.
Recognize that EBS snapshots copied across Regions do not retain their FSR status.
FSR is a property of the snapshot in a specific Region and Availability Zone, and copying the snapshot only copies the block data, not the FSR state.
2
Identify the cause of I/O latency upon volume restoration.
Identify that without FSR enabled on the copied snapshot in the destination Availability Zone, the restored volume must read blocks directly from Amazon S3 (lazy-loading), which causes initial latency.
EBS volumes created from standard snapshots require blocks to be pulled from S3 when first accessed unless FSR is active to pre-initialize the blocks.
3
Determine the required resolution.
FSR must be explicitly enabled on the copied snapshot in us-west-2 for the us-west-2a Availability Zone before restoring the volume.
This pre-initializes the blocks in the destination Availability Zone, ensuring the volume delivers maximum performance immediately upon creation.

Anahtar Kavram

EBS Fast Snapshot Restore (FSR) constraints and behavior across Regions and Availability Zones
Tahmini Süre:2m 30s
Soru 645Soru

A SysOps administrator is configuring event-driven remediation for non-compliant resources. When an AWS Config rule detects a non-compliant Amazon S3 bucket, an Amazon EventBridge rule triggers. The EventBridge rule is configured to target an AWS Systems Manager (SSM) Automation runbook to enable bucket encryption. The administrator has created an IAM role named SSMAutomationServiceRole that SSM will assume to perform the S3 configuration, which has a trust relationship with ssm.amazonaws.com. The administrator also created an IAM role named EventBridgeExecutionRole with a trust relationship for events.amazonaws.com and a policy granting ssm:StartAutomationExecution. When the EventBridge rule triggers, the SSM Automation execution fails to start due to an authorization error. Which of the following explains why the automation execution failed to start?

Cevabı ve açıklamayı göster

Cevap: The EventBridgeExecutionRole does not have the iam:PassRole permission for the SSMAutomationServiceRole.

Cevap

The EventBridgeExecutionRole does not have the iam:PassRole permission for the SSMAutomationServiceRole.
The correct answer is that the EventBridgeExecutionRole lacks the iam:PassRole permission. When configuring an Amazon EventBridge rule to invoke an AWS Systems Manager Automation runbook that runs with a designated service role, the EventBridge execution role must have the iam:PassRole permission for that service role. This ensures that EventBridge has authorization to pass the role to Systems Manager.

Adım Adım Çözüm

1
Analyze the IAM roles and trust relationships involved in the event-driven workflow.
The EventBridgeExecutionRole has a trust relationship with events.amazonaws.com and ssm:StartAutomationExecution permission. The SSMAutomationServiceRole has a trust relationship with ssm.amazonaws.com.
This establishes that EventBridge is authorized to assume its execution role and start the automation, and SSM is authorized to assume its service role.
2
Determine the required permissions when a service passes an IAM role to another service.
The calling service execution role (EventBridgeExecutionRole) must have the iam:PassRole permission for the target role (SSMAutomationServiceRole) that is passed to the executing service (ssm.amazonaws.com).
Security best practices in AWS require explicit permission to pass a service role to prevent privilege escalation.
3
Identify the missing permission leading to the authorization error.
Adding the iam:PassRole permission for the SSMAutomationServiceRole to the EventBridgeExecutionRole resolves the error.
This allows EventBridge to successfully invoke the automation runbook while specifying the service role that the runbook must assume.

Anahtar Kavram

IAM PassRole permissions in event-driven automation targets
Soru 646Soru

An organization has configured an automated remediation workflow to manage costs for underutilized resources. A CloudWatch alarm is set to trigger when the CPU utilization of an Amazon EC2 instance falls below 10%10\% for three consecutive monitoring periods. The alarm is integrated with an Amazon EventBridge rule that targets the `AWS-StopEC2Instance` Systems Manager (SSM) Automation runbook. During a testing phase, the alarm changes to the `ALARM` state, but the EC2 instance continues to run. The administrator checks the EventBridge metrics and notices that the `FailedInvocations` metric for the rule is incrementing, while the `TriggeredRules` metric is also active. No execution history is visible in the Systems Manager Automation console. Which of the following troubleshooting steps should 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 IAM role associated with the EventBridge rule target has a trust policy allowing the `events.amazonaws.com` service principal to assume the role.; Verify that the IAM role associated with the EventBridge rule target has a policy that allows the `ssm:StartAutomationExecution` action on the target runbook.

Cevap

Verify that the IAM role associated with the EventBridge rule target has a trust policy allowing the `events.amazonaws.com` service principal to assume the role, and verify that this IAM role has a policy that allows the `ssm:StartAutomationExecution` action on the target runbook.
To resolve the issue where EventBridge fails to invoke the Systems Manager Automation target, two key configuration components are required. First, the EventBridge rule must use an IAM role that trusts the EventBridge service (`events.amazonaws.com`) so the service can assume it. Second, the IAM role must have an attached policy granting the `ssm:StartAutomationExecution` permission on the Systems Manager runbook resource, enabling EventBridge to launch the automation. Without these, invocations fail, and the execution is never recorded in Systems Manager.

Adım Adım Çözüm

1
Analyze the EventBridge metrics.
The active `TriggeredRules` metric combined with an incrementing `FailedInvocations` metric indicates that EventBridge is successfully catching the state change event but is failing to execute the target action (SSM Automation).
This isolates the failure to the interface between EventBridge and Systems Manager, suggesting a permissions or configuration issue rather than an alarm failure.
2
Verify EventBridge service trust relationship.
Ensure the execution role used by the EventBridge rule contains a trust policy allowing `events.amazonaws.com` to perform `sts:AssumeRole`.
EventBridge must be allowed to assume the specified IAM role to carry out tasks on behalf of the user.
3
Verify execution role permissions.
Ensure the execution role's permission policy allows the `ssm:StartAutomationExecution` action on the target Systems Manager runbook resource ARN.
Without explicit API permission in the policy, the assumed role cannot invoke the Systems Manager runbook, leading to target execution failures.

Anahtar Kavram

IAM Permissions for EventBridge Target Execution
Soru 647Soru

A SysOps Administrator is setting up AWS Systems Manager Patch Manager to automate operating system updates for a fleet of Amazon Linux 2 instances. The administrator has created a custom patch baseline for development environments. However, during testing, the administrator notices that the development instances are still being patched using the default AWS-managed patch baseline instead of the custom one. Which action must the administrator take to ensure the development instances are associated with the custom patch baseline?

Cevabı ve açıklamayı göster

Cevap: Apply a tag to the development instances with the key 'Patch Group' and a custom group value, then register this patch group with the custom patch baseline.

Cevap

Apply a tag to the development instances with the key 'Patch Group' and a custom group value, then register this patch group with the custom patch baseline.
The correct action is to apply a tag to the development instances using the key 'Patch Group' and the designated group name as the value, and then register that patch group name with the custom patch baseline. Patch Manager automatically evaluates this tag to redirect the instances from the default baseline to the custom baseline.

Adım Adım Çözüm

1
Create a custom patch baseline in AWS Systems Manager Patch Manager and specify the patch rules.
A custom patch baseline exists but is not yet associated with any specific instances.
Before mapping instances, the baseline must be defined.
2
Register a patch group name with the custom patch baseline.
The baseline is configured to apply to any instances that belong to the registered patch group.
This establishes the logical link between the baseline and a group identifier.
3
Apply a resource tag to the target EC2 instances using the case-sensitive key 'Patch Group' and the registered patch group name as the value.
Systems Manager Patch Manager detects the tag and routes the instances to use the custom patch baseline instead of the default baseline.
AWS Systems Manager uses the exact tag key 'Patch Group' to associate managed nodes with patch baselines.

Anahtar Kavram

AWS Systems Manager Patch Manager uses the case-sensitive tag key 'Patch Group' to map managed instances to custom patch baselines.
Tahmini Süre:1m 0s
Soru 648Soru

A SysOps Administrator is using AWS Elastic Disaster Recovery (AWS DRS) to replicate an on-premises database server to AWS. The administrator has configured the default EC2 Launch Template in AWS DRS to attach a specific IAM instance profile to the recovery instance upon launch. However, when the administrator attempts to launch a recovery drill, the launch fail status is returned immediately. A review of AWS CloudTrail logs reveals an authorization error related to the IAM role assignment during the EC2 RunInstances API call. Which action will resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Add the iam:PassRole permission for the recovery instance's IAM role to the IAM policy of the SysOps Administrator.

Cevap

Add the iam:PassRole permission for the recovery instance's IAM role to the IAM policy of the SysOps Administrator.
When using AWS Elastic Disaster Recovery (AWS DRS), launching a drill or recovery instance initiates a workflow that runs under the context of the IAM user or role starting the action. If the EC2 Launch Template is configured to attach an IAM instance profile to the launched instance, the initiating IAM identity must have the iam:PassRole permission for the target IAM role. Without this permission, the EC2 RunInstances API call fails with an authorization error.

Adım Adım Çözüm

1
Analyze the CloudTrail log error for the failed DRS recovery drill launch.
Identify that the RunInstances API call failed because the user launching the instance is not authorized to perform the PassRole action on the target IAM role.
To attach an IAM role to an EC2 instance, the initiating user must have permission to pass that role to the EC2 service.
2
Modify the IAM policy of the SysOps Administrator initiating the DRS launch.
The SysOps Administrator's IAM policy is updated to include the iam:PassRole permission targeting the specific ARN of the recovery instance's IAM role.
This authorizes the administrator's IAM identity to pass the role to the EC2 service during the DRS recovery drill.
3
Re-run the AWS DRS recovery drill.
The DRS recovery drill launches successfully, and the recovery EC2 instance starts with the configured IAM instance profile attached.
The permission issue has been resolved, allowing the EC2 service to assume the role on behalf of the instance.

Anahtar Kavram

AWS DRS launches recovery instances using the credentials of the user/role initiating the launch, requiring that user/role to have the iam:PassRole permission to attach an IAM role to the launched EC2 instance.
Soru 649Soru

A SysOps Administrator is deploying a conformance pack containing an AWS Config rule to evaluate EBS volume encryption. The administrator configures automatic remediation for the rule using an AWS Systems Manager (SSM) Automation document. The remediation is configured to encrypt non-compliant volumes using a customer managed key (CMK) in AWS Key Management Service (AWS KMS).

Although the administrator has attached an IAM policy to the SSM Automation service role that allows all KMS actions (kms:*), the automatic remediation fails. The execution history indicates a 'KMS Access Denied' error.

Which of the following explains the cause of this issue?

Cevabı ve açıklamayı göster

Cevap: The key policy of the customer managed key does not explicitly permit the SSM Automation service role to perform the required KMS operations.

Cevap

The key policy of the customer managed key does not explicitly permit the SSM Automation service role to perform the required KMS operations.
For customer managed KMS keys, key policies are the primary mechanism for access control. If a key policy does not explicitly permit an IAM principal (in this case, the SSM Automation service role), or does not delegate permission to the AWS account to use IAM policies for access control, the principal will be denied access regardless of its attached IAM policies.

Adım Adım Çözüm

1
Identify the service executing the remediation.
The remediation is executed by Systems Manager Automation using the SSM service role, not by the AWS Config service itself.
This determines which principal needs permissions for the KMS key.
2
Analyze KMS evaluation logic for customer managed keys.
Access to a customer managed key requires permission to be granted in the key policy. An IAM policy on the principal is not sufficient if the key policy does not delegate permissions to the account or explicitly trust the principal.
To resolve KMS Access Denied errors for service roles using customer managed keys, the key policy must be updated.

Anahtar Kavram

AWS Config automatic remediation executes Systems Manager Automation documents. When encrypting resources using AWS KMS customer managed keys during remediation, the key policy must explicitly grant the SSM service role access to the key.
Soru 650Soru

A SysOps administrator is creating an Amazon Kinesis Data Firehose delivery stream that must write log data to an Amazon S3 bucket. The administrator has already created an IAM role with the necessary S3 permissions and a trust policy that allows Kinesis Firehose to assume the role. However, when the administrator attempts to create the delivery stream using this role, the operation fails with an authorization error.

Which IAM permission must be granted to the SysOps administrator's IAM policy to resolve this issue?

Cevabı ve açıklamayı göster

Cevap: iam:PassRole

Cevap

The permission that allows the administrator to pass the IAM role to the AWS service is iam:PassRole.
The correct answer is the permission that allows an administrator to pass an IAM role to an AWS service (such as Kinesis Data Firehose) so that the service can assume the role and perform actions on their behalf. The iam:PassRole permission must be explicitly granted in the administrator's IAM policy for this operation to succeed.

Adım Adım Çözüm

1
Identify the action causing the failure.
The SysOps administrator is attempting to associate an IAM role with Amazon Kinesis Data Firehose, which is a role delegation action.
When configuring AWS services to act on behalf of a user, the user must have permission to pass the role to the service.
2
Determine the required permission for role delegation.
The required permission is iam:PassRole, which must be added to the administrator's IAM policy.
This permission prevents users from passing highly privileged roles to services they should not configure.

Anahtar Kavram

Delegating IAM roles to AWS services requires the iam:PassRole permission on the user or role performing the configuration.
Tahmini Süre:45s
Soru 651Soru

A company hosts its primary web application using an Amazon Route 53 Alias record at the zone apex pointing to an Amazon CloudFront distribution. The company wants to configure an active-passive disaster recovery solution that automatically routes traffic to a secondary static backup website hosted on an Amazon S3 bucket if the primary CloudFront distribution becomes unavailable. During configuration, the SysOps Administrator observes that the 'Evaluate Target Health' option is not supported for the CloudFront Alias record.

Which two configuration steps must the SysOps Administrator perform to establish this failover mechanism? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create an Amazon Route 53 health check that monitors the primary website endpoint via HTTPS, and associate this health check with the primary CloudFront Alias record.; Create a secondary Alias A record at the zone apex pointing to the Amazon S3 static website endpoint, select the Failover routing policy, and set the Failover Record Type to Secondary.

Cevap

The correct configuration requires creating a Route 53 health check to monitor the primary website endpoint and associating it with the primary CloudFront Alias record, and creating a secondary Alias A record at the zone apex pointing to the Amazon S3 static website endpoint with the Failover routing policy set to Secondary.
To configure active-passive DNS failover at the zone apex when using a CloudFront distribution as the primary endpoint, the administrator must create a Route 53 health check that directly monitors the primary endpoint and associate it with the primary Alias record (since CloudFront does not support the 'Evaluate Target Health' option). Additionally, the secondary record must be an Alias A record pointing to the S3 bucket website endpoint because CNAME records are not permitted at the zone apex.

Adım Adım Çözüm

1
Analyze the Route 53 Alias record constraints for CloudFront distributions.
Recognize that 'Evaluate Target Health' is not supported for CloudFront distribution targets.
Determines that a custom Route 53 health check must be created to monitor the primary application endpoint.
2
Define the routing policy and record type for the primary and secondary endpoints.
Assign the Failover routing policy to both records, configuring the primary record as Primary and the secondary record as Secondary.
Establishes the active-passive relationship between the main site and the backup site.
3
Select the correct DNS record type for the zone apex.
Configure an Alias A record for the S3 static website endpoint instead of a CNAME.
Ensures compliance with DNS specifications, which prohibit CNAME records at the zone apex.

Anahtar Kavram

Route 53 Active-Passive Failover with CloudFront and S3 at the Zone Apex
Soru 652Soru

A company runs a critical microservice on Amazon ECS using the AWS Fargate launch type behind an Application Load Balancer (ALB). A SysOps administrator is configuring a Blue/Green deployment using AWS CodeDeploy. The deployment must satisfy the following conditions:
- The new task definition version must be deployed and validated using a dedicated test listener port before routing production traffic.
- Production traffic must be shifted to the new version gradually over 10 minutes, with 10% shifted every minute.
- CodeDeploy must have the authority to update the ECS service and run tasks with the required task execution role.

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

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

Cevabı ve açıklamayı göster

Cevap: Configure the CodeDeploy deployment group to use the CodeDeployDefault.ECSLinear10PercentEvery1Minute traffic shifting configuration, and specify a test listener port on the Application Load Balancer.; Attach a policy to the CodeDeploy service role that grants the iam:PassRole permission for the ECS task execution role and task role.

Cevap

To satisfy the deployment requirements, the administrator must configure the CodeDeploy deployment group with the CodeDeployDefault.ECSLinear10PercentEvery1Minute traffic shifting option and specify a test listener port on the Application Load Balancer. Additionally, the administrator must attach a policy to the CodeDeploy service role that grants the iam:PassRole permission for the ECS task execution role and task role.
To perform an ECS Blue/Green deployment using CodeDeploy, a deployment group must define the traffic shifting style (such as CodeDeployDefault.ECSLinear10PercentEvery1Minute) and target group configuration. To validate the replacement tasks before routing production traffic, a test listener port is configured. Furthermore, CodeDeploy needs authorization to pass the ECS task execution role and task role to the Amazon ECS service during task creation, which requires the iam:PassRole permission in the CodeDeploy service role's permissions policy.

Adım Adım Çözüm

1
Determine the deployment control method and validation mechanism.
Identify that AWS CodeDeploy must be used with a linear traffic shifting setting (ECSLinear10PercentEvery1Minute) and a test listener port on the Application Load Balancer.
This meets the requirements of shifting traffic 10% per minute and verifying the new version prior to redirecting production traffic.
2
Verify required IAM permissions for CodeDeploy to interact with ECS.
Determine that CodeDeploy must be allowed to pass the ECS task execution role and task role to the ECS service using the iam:PassRole permission.
When CodeDeploy updates the ECS service with the new task definition, it acts on behalf of the administrator and requires permission to pass the associated roles.
3
Identify why other options do not meet the criteria.
Rule out rolling updates as they lack native blue/green traffic shifting; rule out Route 53 routing since DNS cannot target ALB-managed ECS tasks individually; and rule out trust relationship modifications as they do not replace standard iam:PassRole policies.
Eliminating invalid configurations confirms the two correct actions.

Anahtar Kavram

ECS Blue/Green Deployments with AWS CodeDeploy and Identity and Access Management (IAM) permissions
Soru 653Soru

A SysOps administrator is configuring automated, event-driven remediation for non-compliant Amazon S3 buckets using AWS Config. The administrator sets up the AWS Config rule 's3-bucket-public-read-prohibited' and configures the AWS Systems Manager (SSM) Automation runbook 'AWS-ConfigureS3BucketPublicAccessBlock' as the remediation action. However, when the Config rule identifies a non-compliant bucket, the automatic remediation fails to execute with an access denied error. Which combination of configuration actions is required to resolve this issue and ensure the remediation executes successfully? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Grant the SysOps administrator the 'iam:PassRole' permission for the IAM service role specified in the remediation action configuration.; Ensure the IAM service role specified in the remediation action configuration has a trust policy that allows the 'ssm.amazonaws.com' service principal to assume it, along with the permissions to modify S3 public access settings.

Cevap

To resolve the access denied error during remediation, the SysOps administrator must be granted permission to pass the remediation execution role, and the role itself must trust the Systems Manager service principal and have S3 configuration permissions.
For AWS Config remediation via Systems Manager to function, the SysOps administrator must have 'iam:PassRole' permissions to pass the execution role, and the execution role must trust the Systems Manager service ('ssm.amazonaws.com') and have policies allowing the required modifications on S3.

Adım Adım Çözüm

1
Analyze the IAM service role trust policy and permissions.
Ensure the role trusts the Systems Manager principal ('ssm.amazonaws.com') and has policies permitting S3 write/update actions.
Systems Manager Automation executes the actual API calls to modify the S3 resource and requires temporary authorization via STS assume role.
2
Analyze the administrator's IAM permissions.
Ensure the user has an IAM policy allowing the 'iam:PassRole' action targeting the service role.
AWS services require validation that the user configuring the service has permission to delegate that specific role.

Anahtar Kavram

Configuring event-driven remediation in AWS Config using Systems Manager Automation with the appropriate trust relationships and passrole permissions.
Tahmini Süre:1m 30s
Soru 654Soru

A SysOps Administrator is configuring monitoring for a database backup process. The backup application streams JSON-formatted logs to an Amazon CloudWatch Logs group. A typical log event has the following structure:

{
"backupId": "backup-98234",
"status": "Failed",
"durationSeconds": 1450,
"database": "prod-db-01"
}

The administrator needs to monitor the duration of failed backups. Specifically, they want to create a custom CloudWatch metric that records the value of `durationSeconds` only when `status` is equal to `"Failed"`. To avoid alarm flapping and false alerts when no failures occur, the custom metric must report a value of `0` during periods with no matching log events.

Which configuration should the administrator use to achieve this?

Cevabı ve açıklamayı göster

Cevap: Create a metric filter with the filter pattern { .status = "Failed" }. Configure the metric transformation with a Metric Value of .durationSeconds and a Default Value of 0.

Cevap

Create a metric filter with the filter pattern { .status = "Failed" }. Configure the metric transformation with a Metric Value of .durationSeconds and a Default Value of 0.
To extract a specific value from a JSON log event and publish it as a metric, you must create a metric filter with a pattern that matches the target JSON key (e.g., `{ .status = "Failed" }`). In the metric transformation configuration, specifying `.durationSeconds` as the Metric Value extracts the actual duration of the failed backup. Specifying a Default Value of `0` ensures that a value is reported to CloudWatch even when no matching log events occur, preventing the metric from reporting missing data and keeping associated alarms from entering an INSUFFICIENT_DATA state.

Adım Adım Çözüm

1
Define the JSON filter pattern to match the failed backup condition.
The pattern `{ $.status = "Failed" }` matches any JSON log event where the status property equals "Failed".
This isolates the subset of log events containing the data to be measured.
2
Configure the metric value extraction settings in the metric transformation.
Set the Metric Value to `$.durationSeconds`.
This tells CloudWatch Logs to extract the numeric value of the durationSeconds key from the matched log events and use it as the metric data point.
3
Configure the default value mapping in the metric transformation.
Set the Default Value to `0`.
Setting a default value of 0 ensures that CloudWatch reports a 0 value when no events match the filter pattern, preventing the metric from reporting missing data and avoiding false alarms.

Anahtar Kavram

CloudWatch Logs Metric Filters allow extracting values from JSON-structured logs to publish custom metrics, using default values to handle periods without matching logs.
Tahmini Süre:1m 30s
Soru 655Soru

A SysOps Administrator is managing an Amazon S3 Cross-Region Replication (CRR) setup between a source bucket in us-east-1 and a destination bucket in us-west-2. The buckets store critical application logs encrypted with AWS KMS customer managed keys (CMKs) in both regions. The administrator notes two issues: existing logs uploaded before replication was enabled are missing from the destination bucket, and when users delete logs in the source bucket, the corresponding delete markers are not appearing in the destination bucket. Which combination of actions should the administrator take to resolve these issues? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create an Amazon S3 Batch Replication job to replicate the objects that were present in the source bucket before replication was enabled.; Update the replication rule in the source bucket configuration to enable delete marker replication.

Cevap

Create an Amazon S3 Batch Replication job to replicate the objects that were present in the source bucket before replication was enabled, and update the replication rule in the source bucket configuration to enable delete marker replication.
To replicate objects that existed before replication was configured, Amazon S3 Batch Replication must be used. Additionally, to propagate delete markers resulting from simple delete operations on the source bucket, delete marker replication must be explicitly enabled in the replication rule.

Adım Adım Çözüm

1
Address the replication of existing objects.
Determine that S3 replication only automatically replicates new objects or updates after the rule is configured. For existing objects, S3 Batch Replication must be initiated.
This copies objects that existed prior to replication enablement.
2
Address the replication of delete markers.
Recognize that by default, S3 does not replicate delete markers from the source to the destination bucket. Enable the delete marker replication option in the replication rule settings.
This ensures that simple deletes in the source bucket propagate as delete markers in the destination bucket.
3
Validate the prerequisites for replication.
Ensure that versioning remains enabled on both buckets and that the IAM replication role has correct permissions (decrypting source objects and encrypting/writing to the destination).
Ensures the entire replication process remains functional without breaking security or versioning constraints.

Anahtar Kavram

Amazon S3 replication options for existing objects and delete markers.
Soru 656Soru

A SysOps Administrator is monitoring a message-processing application that publishes execution logs to an Amazon CloudWatch Logs group. The log events are formatted in JSON as shown in the following example:

{
"queue": "task-worker",
"msg_id": "m-9941",
"duration": 6.2,
"status": "DLQ_REDIRECT"
}

The Administrator wants to extract the message processing duration as a custom CloudWatch metric named `DLQProcessingTime` under the namespace `CustomWorker`, but only for messages that are redirected to the dead-letter queue where the `status` field equals `"DLQ_REDIRECT"`.

Which TWO configuration steps must the Administrator perform to extract this metric?

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

Cevabı ve açıklamayı göster

Cevap: Create a CloudWatch Logs metric filter with the filter pattern { .status = "DLQ_REDIRECT" }.; Configure the metric transformation with a Metric Value of .duration and Namespace of CustomWorker.

Cevap

The SysOps Administrator must create a CloudWatch Logs metric filter using the JSON filter pattern { .status = "DLQ_REDIRECT" } and configure the metric transformation with a Metric Value of .duration and Namespace of CustomWorker.
To extract a metric from JSON logs, two actions are required: defining the filter pattern to match the target log events and setting up the metric transformation to specify where the metric value comes from. The filter pattern `{ .status = "DLQ_REDIRECT" }` correctly matches only the subset of events that have been redirected. The metric transformation mapping the value to `.duration` successfully extracts the execution duration variable and registers it in the `CustomWorker` namespace.

Adım Adım Çözüm

1
Define a filter pattern to match JSON fields.
Created a filter pattern `{ $.status = "DLQ_REDIRECT" }` that evaluates only logs where the JSON property `status` is equal to the specified string.
This filter filters out unrelated logs so that the metric is only calculated from events redirected to the dead-letter queue.
2
Define the metric transformation rules.
Configured the metric transformation mapping `DLQProcessingTime` as the metric name, `CustomWorker` as the namespace, and `$.duration` as the metric value source.
The metric value source tells CloudWatch Logs which numeric field in the JSON structure represents the metric value to publish.

Anahtar Kavram

CloudWatch Logs Metric Filters with JSON Log Data
Tahmini Süre:1m 30s
Soru 657Soru

A SysOps administrator is configuring automatic rotation for a database credential stored as a secret in AWS Secrets Manager. The database is an Amazon Aurora PostgreSQL DB cluster running in a private VPC subnet. The secret is encrypted using a customer managed AWS KMS key. The administrator configures a custom AWS Lambda function to handle the rotation, deploying it within the same VPC. During testing, the rotation fails, and the CloudWatch Logs for the Lambda rotation function indicate that it is unable to decrypt the current database credential to perform the login test. Which two actions should the SysOps administrator take to resolve this issue? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Add a statement to the KMS key policy of the customer managed key that allows the Lambda rotation function's execution role to perform kms:Decrypt and kms:GenerateDataKey operations.; Attach an IAM policy to the Lambda rotation function's execution role that grants permissions to perform secretsmanager:GetSecretValue, secretsmanager:DescribeSecret, and secretsmanager:PutSecretValue on the secret.

Cevap

To resolve the rotation issue, the administrator must add a statement to the KMS key policy of the customer managed key to allow the Lambda rotation function's execution role to perform decrypt and key generation operations, and attach an IAM policy to the Lambda rotation function's execution role that grants permission to retrieve and modify the secret.
The custom Lambda rotation function requires standard Secrets Manager API permissions (GetSecretValue, DescribeSecret, and PutSecretValue) to interact with the secret metadata and stages. Furthermore, because the secret is encrypted with a customer managed KMS key, the key policy must explicitly authorize the Lambda rotation function's execution role to use the key for decryption and key generation.

Adım Adım Çözüm

1
Analyze the decryption failure in the custom Lambda rotation logs.
Determine that the Lambda function's execution role lacks permissions to use the customer managed KMS key to decrypt the secret.
Since a customer managed KMS key is used, access must be delegated to the Lambda execution role in both IAM and the KMS key policy.
2
Modify the KMS key policy.
Add a statement to the KMS key policy of the customer managed key that allows the Lambda rotation function's execution role to perform kms:Decrypt and kms:GenerateDataKey operations.
This enables the Lambda function to decrypt the encrypted secret value retrieved from Secrets Manager.
3
Update the Lambda execution role IAM policy.
Ensure the role has policies granting secretsmanager:GetSecretValue, secretsmanager:DescribeSecret, and secretsmanager:PutSecretValue on the secret.
The rotation Lambda needs these API permissions to read the current password stage and submit the updated password back to Secrets Manager.

Anahtar Kavram

AWS Secrets Manager automated rotation permissions and KMS key policy integration.
Tahmini Süre:2m 30s
Soru 658Soru

An organization implements a multi-account structure where database credentials are centralized in a security account (Account B) using AWS Secrets Manager. A microservice running on an Amazon EC2 instance in a production account (Account A) requires access to one of these secrets. The secret is encrypted using the default AWS managed key `aws/secretsmanager`. The SysOps administrator configures a resource-based policy on the secret in Account B to allow the EC2 instance's IAM role in Account A to call `secretsmanager:GetSecretValue`. The IAM role in Account A has also been granted permissions to call `secretsmanager:GetSecretValue` on the secret's ARN. However, the EC2 instance receives an `AccessDeniedException` when attempting to retrieve the credential.

Which configuration adjustment will resolve this access issue?

Cevabı ve açıklamayı göster

Cevap: Re-encrypt the secret in Account B using a customer managed KMS key, grant the IAM role in Account A permission to perform `kms:Decrypt` in its IAM policy, and update the customer managed KMS key policy in Account B to allow `kms:Decrypt` for the IAM role in Account A.

Cevap

Re-encrypt the secret in Account B using a customer managed KMS key, grant the IAM role in Account A permission to perform `kms:Decrypt` in its IAM policy, and update the customer managed KMS key policy in Account B to allow `kms:Decrypt` for the IAM role in Account A.
To enable cross-account access to an AWS Secrets Manager secret, the secret must be encrypted with a customer managed KMS key (CMK). The default AWS managed KMS key (`aws/secretsmanager`) has an immutable key policy that cannot be altered to grant cross-account permissions. Once a customer managed KMS key is selected, three permissions must align: the resource policy on the secret in Account B must allow read access; the customer managed key policy in Account B must explicitly permit `kms:Decrypt` for the external identity; and the IAM policy of the role in Account A must permit both secret retrieval and key decryption.

Adım Adım Çözüm

1
Analyze the encryption key used for the secret.
The secret is encrypted using the default AWS managed key `aws/secretsmanager`.
Default AWS managed KMS keys cannot be used for cross-account access because their key policies are managed by AWS and are immutable.
2
Re-encrypt the secret in the source account (Account B).
The secret is now encrypted using a customer managed KMS key (CMK).
Customer managed KMS keys support policy modifications, which are required to delegate cross-account access.
3
Modify the customer managed KMS key policy in Account B.
The key policy allows the IAM role in Account A to execute the `kms:Decrypt` action.
Cross-account access to KMS keys requires the key policy to explicitly delegate access to the external account or its roles.
4
Configure the IAM identity policy in Account A.
The EC2 instance's IAM role includes permissions to call `kms:Decrypt` on the KMS key in Account B.
To access resources in another account, the requesting identity's IAM policy must also explicitly allow the necessary actions on the external resource.

Anahtar Kavram

Cross-account access to AWS Secrets Manager secrets requires using a customer managed KMS key (CMK). The default AWS managed KMS key policy is immutable and cannot be configured to allow cross-account decryption. Access must be granted on both the Secrets Manager resource policy, the KMS key policy, and the caller's IAM policy.
Tahmini Süre:3m 0s
Soru 659Soru

A company's SysOps administrator is reviewing the data transfer costs for a workload running on Amazon EC2 instances in private subnets across two Availability Zones. The instances perform the following tasks:

* Retrieve 20 TB20\text{ TB} of configuration files and static assets monthly from an Amazon S3 bucket in the same AWS Region.
* Publish 15 TB15\text{ TB} of transactional telemetry data monthly to Amazon Kinesis Data Streams in the same AWS Region.

Currently, all traffic to these services is routed through NAT Gateways located in each Availability Zone. Which combination of actions should the SysOps administrator take to achieve the maximum cost savings? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create a gateway VPC endpoint for Amazon S3 and associate it with the private subnet route tables.; Create interface VPC endpoints for Amazon Kinesis Data Streams in the private subnets and enable private DNS.

Cevap

Create a gateway VPC endpoint for Amazon S3 and associate it with the private subnet route tables, and create interface VPC endpoints for Amazon Kinesis Data Streams in the private subnets and enable private DNS.
The correct options are to create a gateway VPC endpoint for Amazon S3 and interface VPC endpoints for Amazon Kinesis Data Streams. Gateway VPC endpoints are free and eliminate the NAT Gateway data processing charges for S3 (0.045/GB).InterfaceVPCendpoints(PrivateLink)forKinesisDataStreamschargeamuchlowerprocessingfee(0.045/GB). Interface VPC endpoints (PrivateLink) for Kinesis Data Streams charge a much lower processing fee ( 0.01/GB) compared to NAT Gateways ($0.045/GB), reducing the overall cost for Kinesis traffic.

Adım Adım Çözüm

1
Analyze S3 traffic cost optimization options.
Using a Gateway VPC Endpoint for Amazon S3 routes S3 traffic directly over the AWS network without traversing the NAT Gateway. Gateway endpoints have no hourly or data processing charges, saving 100%100\% of the NAT Gateway data processing fees (0.045perGB)forthe0.045 per GB) for the 20\text{ TB}$ of data.
Identify the most cost-effective routing method for Amazon S3 traffic originating from private subnets.
2
Analyze Kinesis Data Streams traffic cost optimization options.
Using an Interface VPC Endpoint (AWS PrivateLink) for Kinesis Data Streams routes traffic directly within the VPC. The data processing fee for an interface endpoint is 0.01perGB,comparedtothe0.01 per GB, compared to the 0.045 per GB charged by the NAT Gateway, yielding a net saving of 0.035perGBforthe0.035 per GB for the 15\text{ TB}$ of telemetry data.
Identify the most cost-effective private routing method for AWS services that do not support Gateway VPC Endpoints.
3
Compare the proposed optimizations against other alternatives.
Gateway endpoints are superior to interface endpoints for S3 because gateway endpoints are free. Interface endpoints for Kinesis are superior to NAT Gateways because the per-GB processing fee is lower. Single-AZ NAT Gateway consolidation or Transit Gateway routing introduce additional data transfer or processing charges.
Ensure that the selected options provide the maximum cost savings while maintaining high availability.

Anahtar Kavram

Optimizing VPC data transfer costs by utilizing Gateway and Interface VPC Endpoints to bypass NAT Gateways for AWS service traffic.
Soru 660Soru

A company manages a multi-account AWS environment using AWS Organizations with consolidated billing. A SysOps Administrator has deployed a Tag Policy across the organization to enforce the use of EnvType and CostCenterID tags on all newly created resources. Although the administrator has verified that resources in the member accounts are successfully tagged, these tags are not available as filters or grouping options in AWS Cost Explorer or AWS Budgets. Which two actions must the SysOps Administrator perform to resolve this issue and start tracking costs using these tags? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Sign in to the AWS Organizations management account and activate the EnvType and CostCenterID tags in the Cost Allocation Tags section of the Billing console.; Wait up to 24 hours after activating the tags for them to appear in Cost Explorer and Billing reports.

Cevap

To resolve the issue, the SysOps Administrator must sign in to the AWS Organizations management account, activate the EnvType and CostCenterID tags in the Cost Allocation Tags section of the Billing console, and wait up to 24 hours for the tags to populate in Cost Explorer and Billing reports.
The correct actions are to sign in to the management account and activate the tags in the Billing console, and to wait up to 24 hours for the tags to populate. In an AWS Organizations consolidated billing environment, only the management account has the permissions to activate cost allocation tags. Additionally, AWS requires up to 24 hours to index and display cost data for newly activated tags.

Adım Adım Çözüm

1
Sign in to the AWS Organizations management (payer) account.
Access to the centralized billing and cost management configurations for the entire organization.
Only the management account in a consolidated billing structure has the authority to activate cost allocation tags.
2
Navigate to the Billing and Cost Management console and select Cost Allocation Tags.
Displays a list of active and inactive user-defined and AWS-defined tags.
This is where tag keys applied to resources are registered for billing reports.
3
Select the EnvType and CostCenterID tags, then choose Activate.
The tags are marked as active cost allocation tags.
Activating tags tells AWS to start tracking cost data associated with those tag keys.
4
Wait up to 24 hours for the data to process and become visible.
The tags become available as filters and grouping options in Cost Explorer and AWS Budgets.
AWS billing pipelines require time to process and update cost historical records with the newly activated tags.

Anahtar Kavram

Cost allocation tags do not automatically track cost data upon resource creation or tag policy enforcement. They must be explicitly activated in the AWS Billing console by the management (payer) account of the organization, after which it can take up to 24 hours for the data to appear in tools like Cost Explorer.
Tahmini Süre:1m 30s
ÖncekiSayfa 33 / 49Sonraki
Tüm alıştırma soruları — AWS Certified SysOps Administrator - Associate | Examkin