support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
CrowdStrike
Anthropic
All Vendors
  1. Home
  2. Exams
  3. Amazon
  4. AWS DevOps Engineer Professional

Free AWS DevOps Engineer Professional Exam Braindumps
AWS DevOps Engineer - Professional (DOP-C02) Questions 51–55 (page: 12)

Updated On: 10-Feb-2026
Page 12 of 43
PDF with 429 Questions

An online company uses Amazon EC2 Auto Scaling extensively to provide an excellent customer experience while minimizing the number of running EC2 instances. The company's self-hosted Puppet environment in the application layer manages the con guration of the instances. The IT manager wants the lowest licensing costs and wants to ensure that whenever the EC2 Auto Scaling group scales down, removed EC2 instances are deregistered from the Puppet master as soon as possible.
How can the requirement be met?

  1. At instance launch time, use EC2 user data to deploy the AWS CodeDeploy agent. Use CodeDeploy to install the Puppet agent. When the Auto Scaling group scales out, run a script to register the newly deployed instances to the Puppet master. When the Auto Scaling group scales in, use the EC2 Auto Scaling EC2_INSTANCE_TERMINATING lifecycle hook to trigger de-registration from the Puppet master.
  2. Bake the AWS CodeDeploy agent into the base AMI. When the Auto Scaling group scales out, use CodeDeploy to install the Puppet agent, and execute a script to register the newly deployed instances to the Puppet master. When the Auto Scaling group scales in, use the CodeDeploy ApplicationStop lifecycle hook to run a script to de-register the instance from the Puppet master.
  3. At instance launch time, use EC2 user data to deploy the AWS CodeDeploy agent. When the Auto Scaling group scales out, use CodeDeploy to install the Puppet agent, and run a script to register the newly deployed instances to the Puppet master. When the Auto Scaling group scales in, use the EC2 user data instance stop script to run a script to de-register the instance from the Puppet master.
  4. Bake the AWS Systems Manager agent into the base AMI. When the Auto Scaling group scales out, use the AWS Systems Manager to install the Puppet agent, and run a script to register the newly deployed instances to the Puppet master. When the Auto Scaling group scales in, use the Systems Manager instance stop lifecycle hook to run a script to de-register the instance from the Puppet master.

Answer(s): A



A company uses a series of individual Amazon CloudFormation templates to deploy its multi-Region applications. These templates must be deployed in a speci c order. The company is making more changes to the templates than previously expected and wants to deploy new templates more e ciently. Additionally, the data engineering team must be noti ed of all changes to the templates.
What should the company do to accomplish these goals?

  1. Create an AWS Lambda function to deploy the CloudFormation templates in the required order. Use stack policies to alert the data engineering team.
  2. Host the CloudFormation templates in Amazon S3. Use Amazon S3 events to directly trigger CloudFormation updates and Amazon SNS noti cations.
  3. Implement CloudFormation StackSets and use drift detection to trigger update alerts to the data engineering team.
  4. Leverage CloudFormation nested stacks and stack sets for deployments. Use Amazon SNS to notify the data engineering team.

Answer(s): D


Reference:

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-nested-stacks.html



A company is running an application on Amazon EC2 instances in an Auto Scaling group. Recently, an issue occurred that prevented EC2 instances from launching successfully, and it took several hours for the Support team to discover the issue. The Support team wants to be noti ed by email whenever an EC2 instance does not start successfully.
Which action will accomplish this?

  1. Add a health check to the Auto Scaling group to invoke an AWS Lambda function whenever an instance status is impaired.
  2. Con gure the Auto Scaling group to send a noti cation to an Amazon SNS topic whenever a failed instance launch occurs.
  3. Create an Amazon CloudWatch alarm that invokes an AWS Lambda function when a failed AttachInstances Auto Scaling API call is made.
  4. Create a status check alarm on Amazon EC2 to send a noti cation to an Amazon SNS topic whenever a status check fail occurs.

Answer(s): B


Reference:

https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-sns-noti cations.html#auto-scaling-sns-noti cations Topic 1



A company uses AWS Storage Gateway in le gateway mode in front of an Amazon S3 bucket that is used by multiple resources. In the morning when business begins, users do not see the objects processed by a third party the previous evening. When a DevOps engineer looks directly at the S3 bucket, the data is there, but it is missing in Storage Gateway.
Which solution ensures that all the updated third-party les are available in the morning?

  1. Con gure a nightly Amazon EventBridge (Amazon CloudWatch Events) event to trigger an AWS Lambda function to run the RefreshCache command for Storage Gateway.
  2. Instruct the third party to put data into the S3 bucket using AWS Transfer for SFTP.
  3. Modify Storage Gateway to run in volume gateway mode.
  4. Use S3 same-Region replication to replicate any changes made directly in the S3 bucket to Storage Gateway.

Answer(s): A



A DevOps engineer sets up two Amazon S3 event noti cations for an S3 bucket from the S3 console. Both event noti cations will be invoked when an object PUT action occurs. One event noti cation will invoke an AWS Lambda function if the le su x is .csv. Another event noti cation will invoke an Amazon Simple
Noti cation Service (Amazon SNS) topic if the le su x is .xlsx
The DevOps engineer notices that les with the .csv su x can invoke the Lambda function successfully. However, les with the .xlsx su x cannot invoke the SNS topic.
Which reason explains why the SNS topic is not invoked when .xlsx les are added to the S3 bucket?

  1. Only one event noti cation is allowed from the S3 console.
  2. Amazon S3 needs proper permissions to publish an event noti cation to Amazon SNS.
  3. Lambda has precedence over Amazon SNS in handling the event noti cation.
  4. Amazon SNS is not a valid destination for some S3 event noti cations, including object PUT.

Answer(s): B



  PDF
Viewing page 12 of 43
Viewing questions 56 - 60 out of 429 questions


Post your Comments and Discuss Amazon AWS DevOps Engineer Professional exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!