Exam Bundle

AWS region expansion is a provider decision about building out AWS geographic infrastructure. This does not address the need for An application owner needs to protect its data on self-managed virtual machines. The appropriate Customer data protection responsibility applies because Customers control the protection of their data and encryption choices while AWS secures underlying cloud facilities.

AWS physical facility guards: Protect access to AWS-operated buildings. This does not address the need for An application owner needs to protect its data on self-managed virtual machines. The appropriate Customer data protection responsibility applies because Customers control the protection of their data and encryption choices while AWS secures underlying cloud facilities.

AWS hypervisor patching concerns patching the AWS-managed virtualization layer rather than customers managing their application. This does not address the need for An application owner needs to protect its data on self-managed virtual machines. The appropriate Customer data protection responsibility applies because Customers control the protection of their data and encryption choices while AWS secures underlying cloud facilities.

Customer data authorization: Controls which principals or applications may access customer-managed data. That does not meet the requirement: A startup uses AWS Lambda and wants to know who maintains the underlying compute hardware.

Customer business logic is implemented by the application owner, separate from AWS physical infrastructure duties. That does not meet the requirement: A startup uses AWS Lambda and wants to know who maintains the underlying compute hardware.

Customer application secrets: Require careful access, rotation and storage controls in the customer application. That does not meet the requirement: A startup uses AWS Lambda and wants to know who maintains the underlying compute hardware.

Customer application secrets: Require careful access, rotation and storage controls in the customer application. This does not address the need for A startup uses AWS Lambda and wants to know who maintains the underlying compute hardware. The appropriate AWS managed Lambda infrastructure applies because AWS operates the managed infrastructure underlying Lambda while customers remain responsible for their code and permissions.

Customer data authorization: Controls which principals or applications may access customer-managed data. This does not address the need for A startup uses AWS Lambda and wants to know who maintains the underlying compute hardware. The appropriate AWS managed Lambda infrastructure applies because AWS operates the managed infrastructure underlying Lambda while customers remain responsible for their code and permissions.

Customer business logic is implemented by the application owner, separate from AWS physical infrastructure duties. This does not address the need for A startup uses AWS Lambda and wants to know who maintains the underlying compute hardware. The appropriate AWS managed Lambda infrastructure applies because AWS operates the managed infrastructure underlying Lambda while customers remain responsible for their code and permissions.

Customer data authorization: Controls which principals or applications may access customer-managed data. That does not meet the requirement: Consider this AWS requirement: A team replaces EC2 servers with Lambda and asks who operates physical hosts and service infrastructure.

Customer application secrets: Require careful access, rotation and storage controls in the customer application. That does not meet the requirement: Consider this AWS requirement: A team replaces EC2 servers with Lambda and asks who operates physical hosts and service infrastructure.

Customer business logic is implemented by the application owner, separate from AWS physical infrastructure duties. That does not meet the requirement: Consider this AWS requirement: A team replaces EC2 servers with Lambda and asks who operates physical hosts and service infrastructure.

Customer business logic is implemented by the application owner, separate from AWS physical infrastructure duties. This does not address the need for A team replaces EC2 servers with Lambda and asks who operates physical hosts and service infrastructure. The appropriate AWS managed Lambda infrastructure applies because AWS operates the managed infrastructure underlying Lambda while customers remain responsible for their code and permissions.

Customer data authorization: Controls which principals or applications may access customer-managed data. This does not address the need for A team replaces EC2 servers with Lambda and asks who operates physical hosts and service infrastructure. The appropriate AWS managed Lambda infrastructure applies because AWS operates the managed infrastructure underlying Lambda while customers remain responsible for their code and permissions.

Customer application secrets: Require careful access, rotation and storage controls in the customer application. This does not address the need for A team replaces EC2 servers with Lambda and asks who operates physical hosts and service infrastructure. The appropriate AWS managed Lambda infrastructure applies because AWS operates the managed infrastructure underlying Lambda while customers remain responsible for their code and permissions.

AWS service platform patching updates AWS-managed service components, not application-level data permissions. That does not meet the requirement: A developer deploys Lambda functions containing input validation and needs to own application logic defects.

AWS data-center networking concerns the provider-operated physical network inside AWS facilities. That does not meet the requirement: A developer deploys Lambda functions containing input validation and needs to own application logic defects.

AWS server maintenance covers AWS maintenance of its fleet of underlying physical servers. That does not meet the requirement: A developer deploys Lambda functions containing input validation and needs to own application logic defects.

AWS service platform patching updates AWS-managed service components, not application-level data permissions. This does not address the need for A developer deploys Lambda functions containing input validation and needs to own application logic defects. The appropriate Customer Lambda code responsibility applies because The customer authors and secures the Lambda function code even though AWS manages the serverless platform.

AWS server maintenance covers AWS maintenance of its fleet of underlying physical servers. This does not address the need for A developer deploys Lambda functions containing input validation and needs to own application logic defects. The appropriate Customer Lambda code responsibility applies because The customer authors and secures the Lambda function code even though AWS manages the serverless platform.

AWS data-center networking concerns the provider-operated physical network inside AWS facilities. This does not address the need for A developer deploys Lambda functions containing input validation and needs to own application logic defects. The appropriate Customer Lambda code responsibility applies because The customer authors and secures the Lambda function code even though AWS manages the serverless platform.

AWS service platform patching updates AWS-managed service components, not application-level data permissions. That does not meet the requirement: A technical reviewer evaluates this need: A team asks who must fix insecure business logic inside a serverless function.

AWS data-center networking concerns the provider-operated physical network inside AWS facilities. That does not meet the requirement: A technical reviewer evaluates this need: A team asks who must fix insecure business logic inside a serverless function.

AWS server maintenance covers AWS maintenance of its fleet of underlying physical servers. That does not meet the requirement: A technical reviewer evaluates this need: A team asks who must fix insecure business logic inside a serverless function.

AWS service platform patching updates AWS-managed service components, not application-level data permissions. This does not address the need for A team asks who must fix insecure business logic inside a serverless function. The appropriate Customer Lambda code responsibility applies because The customer authors and secures the Lambda function code even though AWS manages the serverless platform.

AWS data-center networking concerns the provider-operated physical network inside AWS facilities. This does not address the need for A team asks who must fix insecure business logic inside a serverless function. The appropriate Customer Lambda code responsibility applies because The customer authors and secures the Lambda function code even though AWS manages the serverless platform.

AWS server maintenance covers AWS maintenance of its fleet of underlying physical servers. This does not address the need for A team asks who must fix insecure business logic inside a serverless function. The appropriate Customer Lambda code responsibility applies because The customer authors and secures the Lambda function code even though AWS manages the serverless platform.

Customer table authorization: Sets database object permissions and is distinct from provider-run storage hardware maintenance. That does not meet the requirement: A team uses managed Amazon RDS and needs routine database engine patch management as offered by the service.

Customer application query logic is controlled in application code, not by the AWS infrastructure operator. That does not meet the requirement: A team uses managed Amazon RDS and needs routine database engine patch management as offered by the service.

Customer data retention policy: Defines business and legal retention requirements for customer information. That does not meet the requirement: A team uses managed Amazon RDS and needs routine database engine patch management as offered by the service.

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.