Exam simulatorAWS Cloud Practitioner

Correct answer: D. The reliability pillar is about a workload performing its intended function correctly and consistently and recovering from failures; keeping a standby instance in another Availability Zone removes a single point of failure and enables automatic failover. Operational excellence focuses on how operational processes are run, monitored and improved, not on infrastructure redundancy. Sustainability aims to reduce environmental impact, and duplicating resources in another zone does not serve that goal. Performance efficiency is about using computing resources efficiently as demand changes, and a standby replica neither serves traffic nor improves performance.

Correct answer: D. AWS Transform MGN, formerly AWS Application Migration Service, automates rehost (lift-and-shift) migrations: it replicates physical, virtual or other-cloud servers, together with their operating system, applications and databases, and launches them as EC2 instances. AWS DMS migrates data from one database to a target database, but it does not move the server or the rest of its software. AWS SCT converts a database schema from one engine to a different one, which is not needed here. AWS Snowball Edge is a device for transferring large amounts of data offline, not for turning a server into an EC2 instance.

Correct answer: D. Amazon Macie is a data security and privacy service that uses machine learning and pattern matching to discover, classify and help protect sensitive data, such as personal or financial information, stored in Amazon S3 buckets. Amazon GuardDuty detects threats and malicious activity by analyzing logs such as CloudTrail or VPC Flow Logs, but it does not classify object contents. Amazon Inspector looks for software vulnerabilities and network exposure in EC2 instances, container images and Lambda functions. AWS Config assesses and records resource configuration, not file contents.

Correct answer: C. An AWS account is the strongest boundary for resource, security and billing isolation, so separating production from the other environments into different accounts lets you see the costs of each side separately (and you can use one account per environment if you also want to tell testing apart from development), and AWS Organizations can group them without losing that detail. Using different services per environment does not isolate costs and makes testing and production no longer comparable. IAM roles control who can do what, but they do not separate billing. Amazon CloudWatch shows usage and performance metrics; it does not split costs by environment.