A CloudOps engineer is troubleshooting an AWS CloudFormation stack creation that failed. Before the CloudOps engineer can identify the problem, the stack and its resources are deleted. For future deployments, the CloudOps engineer must preserve any resources that CloudFormation successfully created.
What should the CloudOps engineer do to meet this requirement?
By default, when AWS CloudFormation encounters a failure during stack creation, it automatically rolls back and deletes any resources that were successfully created. This behavior makes troubleshooting difficult because the failed and partially created resources are no longer available for inspection.
CloudFormation provides the OnFailure parameter to control this behavior. Setting the parameter to DO_NOTHING instructs CloudFormation to stop stack creation when a failure occurs and retain all successfully created resources. This allows the CloudOps engineer to inspect the environment, review logs, and identify the root cause without redeploying resources.
The DisableRollback parameter controls rollback behavior but does not provide the same explicit behavior control during failure scenarios. Rollback triggers are used for monitoring-based rollback, not for preserving resources on failure. Setting OnFailure to ROLLBACK explicitly enforces deletion, which is the opposite of the requirement.
Therefore, setting the OnFailure parameter to DO_NOTHING is the correct solution.
A company operates compute resources in a VPC and in the company's on-premises data center. The company already has an AWS Direct Connect connection between the VPC and the on-premises data center.
A CloudOps engineer needs to ensure that Amazon EC2 instances in the VPC can resolve DNS names for hosts in the on-premises data center.
Which solution will meet this requirement with the LEAST amount of ongoing maintenance?
Amazon Route 53 Resolver outbound endpoints enable Amazon VPC resources to forward DNS queries to DNS servers that are outside of AWS, such as on-premises DNS servers. Because the company already has AWS Direct Connect in place, DNS queries can be routed privately from the VPC to the on-premises DNS infrastructure without using the public internet.
By creating an outbound endpoint and configuring forwarding rules for the on-premises domains, EC2 instances in the VPC can resolve DNS names dynamically using the existing authoritative DNS servers. This approach requires minimal ongoing maintenance because DNS records continue to be managed centrally in the on-premises DNS system.
Manually populating a private hosted zone or /etc/hosts files would require constant updates and does not scale. Reverse DNS forwarding alone does not solve forward name resolution.
Therefore, using Route 53 Resolver outbound endpoints is the correct solution.
A company's CloudOps engineer is troubleshooting communication between the components of an application. The company configured VPC flow logs to be published to Amazon CloudWatch Logs. However, there are no logs in CloudWatch Logs.
What could be blocking the VPC flow logs from being published to CloudWatch Logs?
VPC Flow Logs require permissions to create log groups and log streams in Amazon CloudWatch Logs. If the IAM role associated with the flow log lacks the logs:CreateLogGroup permission, CloudWatch Logs cannot be created and no logs will appear.
Option B is unrelated because CreateExportTask is used for exporting logs, not publishing them. IPv6 configuration and VPC peering do not prevent flow logs from being delivered.
Ensuring the IAM role has the correct CloudWatch Logs permissions resolves the issue.
A company runs an application on Amazon EC2 that connects to an Amazon Aurora PostgreSQL database. A developer accidentally drops a table from the database, causing application errors. Two hours later, a CloudOps engineer needs to recover the data and make the application functional again.
Which solution will meet this requirement?
In the AWS Cloud Operations and Aurora documentation, when data loss occurs due to human error such as dropped tables, Point-in-Time Recovery (PITR) is the recommended method for restoration. PITR creates a new Aurora cluster restored to a specific time before the failure.
The restored cluster has a new endpoint that must be reconfigured in the application to resume normal operations. AWS does not support performing PITR directly on an existing production database because that would overwrite current data.
Aurora Backtrack (Option A) applies only to Aurora MySQL, not PostgreSQL. Option B is incorrect because PITR cannot be executed in place. Option D refers to an import process from S3, which is unrelated to time-based recovery.
Hence, Option C is correct and follows the AWS CloudOps standard recovery pattern for PostgreSQL workloads.
A company applies user-defined tags to AWS resources. Twenty days after applying the tags, the company notices that the tags cannot be used to filter views in the AWS Cost Explorer console.
What is the reason for this issue?
User-defined tags must be explicitly activated as cost allocation tags in the AWS Billing and Cost Management console before they can be used in Cost Explorer. Simply applying tags to resources is not sufficient.
Once activated, cost allocation tags can take up to 24 hours to appear in Cost Explorer, but they will not appear at all if activation is not performed. The 30-day delay applies only to historical reporting after activation, not to visibility itself.
Cost and Usage Reports and Budgets are not prerequisites for Cost Explorer filtering.
Therefore, the issue occurs because the tags were not activated for cost allocation.
Joseph Torres
19 days agoThomas Hernandez
25 days agoRichard Gonzalez
2 months agoDaniel Edwards
2 months agoHeather Taylor
3 months agoMelissa Hernandez
3 months agoStephen Anderson
3 months agoMichelle Stewart
2 months agoEric Wilson
2 months agoPaul Anderson
2 months agoBrenda Baker
3 months agoJohnna
4 months agoJoseph
4 months agoBeckie
4 months agoWilliam
4 months agoPrecious
5 months agoLetha
5 months agoFatima
5 months agoMozell
5 months agoEvette
6 months agoDell
6 months agoDesmond
6 months agoGiovanna
6 months agoFredric
6 months agoRozella
7 months agoCordell
7 months agoTammara
7 months agoGlory
7 months agoLatanya
8 months agoVerdell
8 months agoDean
8 months agoAugustine
8 months agoSommer
9 months agoSalome
9 months ago