Exam Bundle

Customer table authorization: Sets database object permissions and is distinct from provider-run storage hardware maintenance. This does not address the need for A team uses managed Amazon RDS and needs routine database engine patch management as offered by the service. The appropriate AWS managed RDS platform maintenance applies because Amazon RDS manages specified database engine and underlying host maintenance while customers manage data and access.

Customer data retention policy: Defines business and legal retention requirements for customer information. This does not address the need for A team uses managed Amazon RDS and needs routine database engine patch management as offered by the service. The appropriate AWS managed RDS platform maintenance applies because Amazon RDS manages specified database engine and underlying host maintenance while customers manage data and access.

Customer application query logic is controlled in application code, not by the AWS infrastructure operator. This does not address the need for A team uses managed Amazon RDS and needs routine database engine patch management as offered by the service. The appropriate AWS managed RDS platform maintenance applies because Amazon RDS manages specified database engine and underlying host maintenance while customers manage data and access.

Customer table authorization: Sets database object permissions and is distinct from provider-run storage hardware maintenance. That does not meet the requirement: An app moves a database from EC2 to RDS to reduce database software maintenance work.

Customer data retention policy: Defines business and legal retention requirements for customer information. That does not meet the requirement: An app moves a database from EC2 to RDS to reduce database software maintenance work.

Customer application query logic is controlled in application code, not by the AWS infrastructure operator. That does not meet the requirement: An app moves a database from EC2 to RDS to reduce database software maintenance work.

Customer data retention policy: Defines business and legal retention requirements for customer information. This does not address the need for An app moves a database from EC2 to RDS to reduce database software maintenance work. The appropriate AWS managed RDS platform maintenance applies because Amazon RDS manages specified database engine and underlying host maintenance while customers manage data and access.

Customer application query logic is controlled in application code, not by the AWS infrastructure operator. This does not address the need for An app moves a database from EC2 to RDS to reduce database software maintenance work. The appropriate AWS managed RDS platform maintenance applies because Amazon RDS manages specified database engine and underlying host maintenance while customers manage data and access.

Customer table authorization: Sets database object permissions and is distinct from provider-run storage hardware maintenance. This does not address the need for An app moves a database from EC2 to RDS to reduce database software maintenance work. The appropriate AWS managed RDS platform maintenance applies because Amazon RDS manages specified database engine and underlying host maintenance while customers manage data and access.

AWS underlying hardware maintenance keeps AWS-owned physical equipment operational; customer database authorization remains separate. That does not meet the requirement: Consider this AWS requirement: A company uses Amazon RDS for customer records and needs to assign responsibility for data classification and permissions.

AWS service infrastructure monitoring observes AWS-managed service infrastructure, not access rules inside customer applications. That does not meet the requirement: Consider this AWS requirement: A company uses Amazon RDS for customer records and needs to assign responsibility for data classification and permissions.

AWS power protection maintains power resilience for AWS-operated data-center infrastructure. That does not meet the requirement: Consider this AWS requirement: A company uses Amazon RDS for customer records and needs to assign responsibility for data classification and permissions.

AWS power protection maintains power resilience for AWS-operated data-center infrastructure. This does not address the need for A company uses Amazon RDS for customer records and needs to assign responsibility for data classification and permissions. The appropriate Customer database data and access control applies because Managed databases do not remove the customer's responsibility for application data, accounts and permissions.

AWS underlying hardware maintenance keeps AWS-owned physical equipment operational; customer database authorization remains separate. This does not address the need for A company uses Amazon RDS for customer records and needs to assign responsibility for data classification and permissions. The appropriate Customer database data and access control applies because Managed databases do not remove the customer's responsibility for application data, accounts and permissions.

AWS service infrastructure monitoring observes AWS-managed service infrastructure, not access rules inside customer applications. This does not address the need for A company uses Amazon RDS for customer records and needs to assign responsibility for data classification and permissions. The appropriate Customer database data and access control applies because Managed databases do not remove the customer's responsibility for application data, accounts and permissions.

AWS service infrastructure monitoring observes AWS-managed service infrastructure, not access rules inside customer applications. That does not meet the requirement: A regulated team must control who can read records in its managed RDS database.

AWS underlying hardware maintenance keeps AWS-owned physical equipment operational; customer database authorization remains separate. That does not meet the requirement: A regulated team must control who can read records in its managed RDS database.

AWS power protection maintains power resilience for AWS-operated data-center infrastructure. That does not meet the requirement: A regulated team must control who can read records in its managed RDS database.

AWS underlying hardware maintenance keeps AWS-owned physical equipment operational; customer database authorization remains separate. This does not address the need for A regulated team must control who can read records in its managed RDS database. The appropriate Customer database data and access control applies because Managed databases do not remove the customer's responsibility for application data, accounts and permissions.

AWS power protection maintains power resilience for AWS-operated data-center infrastructure. This does not address the need for A regulated team must control who can read records in its managed RDS database. The appropriate Customer database data and access control applies because Managed databases do not remove the customer's responsibility for application data, accounts and permissions.

AWS service infrastructure monitoring observes AWS-managed service infrastructure, not access rules inside customer applications. This does not address the need for A regulated team must control who can read records in its managed RDS database. The appropriate Customer database data and access control applies because Managed databases do not remove the customer's responsibility for application data, accounts and permissions.

All security outsourced to AWS incorrectly removes customer responsibility for identities, data and configurations. That does not meet the requirement: A technical reviewer evaluates this need: A team compares running a database on EC2 with using Amazon RDS to understand which operations move to AWS.

Identical duties for all services: Ignores how shared-responsibility boundaries differ for EC2 and fully managed services. That does not meet the requirement: A technical reviewer evaluates this need: A team compares running a database on EC2 with using Amazon RDS to understand which operations move to AWS.

All infrastructure outsourced to customer incorrectly makes customers responsible for AWS-operated physical infrastructure. That does not meet the requirement: A technical reviewer evaluates this need: A team compares running a database on EC2 with using Amazon RDS to understand which operations move to AWS.

Identical duties for all services: Ignores how shared-responsibility boundaries differ for EC2 and fully managed services. This does not address the need for A team compares running a database on EC2 with using Amazon RDS to understand which operations move to AWS. The appropriate Service-dependent responsibility boundary applies because Responsibility shifts with service abstraction; moving to managed services transfers certain platform tasks to AWS.

All infrastructure outsourced to customer incorrectly makes customers responsible for AWS-operated physical infrastructure. This does not address the need for A team compares running a database on EC2 with using Amazon RDS to understand which operations move to AWS. The appropriate Service-dependent responsibility boundary applies because Responsibility shifts with service abstraction; moving to managed services transfers certain platform tasks to AWS.

All security outsourced to AWS incorrectly removes customer responsibility for identities, data and configurations. This does not address the need for A team compares running a database on EC2 with using Amazon RDS to understand which operations move to AWS. The appropriate Service-dependent responsibility boundary applies because Responsibility shifts with service abstraction; moving to managed services transfers certain platform tasks to AWS.

Identical duties for all services: Ignores how shared-responsibility boundaries differ for EC2 and fully managed services. That does not meet the requirement: An architect compares VM-managed and platform-managed offerings to understand shifting maintenance duties.

All infrastructure outsourced to customer incorrectly makes customers responsible for AWS-operated physical infrastructure. That does not meet the requirement: An architect compares VM-managed and platform-managed offerings to understand shifting maintenance duties.

All security outsourced to AWS incorrectly removes customer responsibility for identities, data and configurations. That does not meet the requirement: An architect compares VM-managed and platform-managed offerings to understand shifting maintenance duties.

All infrastructure outsourced to customer incorrectly makes customers responsible for AWS-operated physical infrastructure. This does not address the need for An architect compares VM-managed and platform-managed offerings to understand shifting maintenance duties. The appropriate Service-dependent responsibility boundary applies because Responsibility shifts with service abstraction; moving to managed services transfers certain platform tasks to AWS.

Identical duties for all services: Ignores how shared-responsibility boundaries differ for EC2 and fully managed services. This does not address the need for An architect compares VM-managed and platform-managed offerings to understand shifting maintenance duties. The appropriate Service-dependent responsibility boundary applies because Responsibility shifts with service abstraction; moving to managed services transfers certain platform tasks to AWS.

All security outsourced to AWS incorrectly removes customer responsibility for identities, data and configurations. This does not address the need for An architect compares VM-managed and platform-managed offerings to understand shifting maintenance duties. The appropriate Service-dependent responsibility boundary applies because Responsibility shifts with service abstraction; moving to managed services transfers certain platform tasks to AWS.