A developer for a county tax service chains three AssumeRole hops because a blog sample did, which complicates audits. What should the team prefer?
Select an answer to reveal the explanation.
Short Explanation
Each extra AssumeRole hop is another hallway camera auditors have to rewind. Keep the path short and the trust policy readable. Blog-driven chain gymnastics and shared long-term keys just muddy the trail.
Full Explanation
Role chaining increases operational and audit complexity and can obscure who can obtain which permissions. Developers should design minimal, clear AssumeRole paths and maintain explicit trust policies for intended principals. Additional unnecessary hops, shared long-term keys, or empty trust controls are anti-patterns.