Question 1 Todo.io wants a multi-account setup with central logging, single sign-on and guardrails, built the AWS-recommended way, with the least work. What should it use?
Choose one answer Learn it: AWS Control Tower · Set up AWS: Day 0 with Control Tower · Landing zone
Question 2 A teammate says that once Todo.io uses Control Tower, it no longer uses AWS Organizations. Which statement is true?
Choose one answer Control Tower sets up and governs Organizations, IAM Identity Center, CloudTrail and Config. It doesn't replace them. Correct. The organization, the OUs and the SCPs are all still there. Control Tower manages them for you. Control Tower replaces Organizations with its own account system. Not this one. Control Tower runs on top of Organizations. Control Tower is only a dashboard; it changes nothing. Not this one. It creates accounts, applies controls and sets up logging and sign-in. Control Tower runs separately inside each member account. Not this one. It runs from the management account and governs the accounts below it.
Learn it: AWS Control Tower
Question 3 A teammate edits one of Control Tower's SCPs by hand in the Organizations console. What does Control Tower do?
Choose one answer It reports drift, so the landing zone can be repaired to match its intended setup. Correct. Control Tower notices changes made outside it. Fixing the drift puts its managed resources back as they should be. Nothing. Changes made in the Organizations console are invisible to it. Not this one. Control Tower watches the resources it manages, wherever they are changed. It deletes the account that was changed. Not this one. It never deletes accounts on its own. It blocks the edit before it happens. Not this one. The edit goes through. Control Tower reports it afterwards.
Learn it: AWS Control Tower
Question 4 Todo.io had three accounts before it set up Control Tower. Can they be governed by it?
Choose one answer Yes. Existing accounts in the organization can be enrolled. Correct. Enrolling an account applies the landing zone's logging, guardrails and sign-in to it. No. They have to be closed and recreated with Account Factory. Not this one. Enrollment exists so that doesn't have to happen. Only by moving their workloads into the management account. Not this one. Workloads should never move into the management account. Only their root users can be governed. Not this one. Enrollment governs the whole account.
Learn it: AWS Control Tower
Question 5 What does "AWS Control Tower" mean?
Choose one answer Learn it: AWS Control Tower
Question 6 Which term is this? "Sets up and governs a multi-account AWS environment (a landing zone) for you."
Choose one answer Learn it: AWS Control Tower
Question 7 Which AWS term is described by this analogy? "A developer who builds the whole apartment complex to code, then inspects it regularly."
Choose one answer Learn it: AWS Control Tower