A project manager is onboarding five developers who all need to build and test skills in a shared watsonx Assistant instance. The manager wants to avoid shared credentials and ensure that actions by each developer can be individually audited. What is the recommended IBM Cloud access management approach?

IBM Cloud IAM supports inviting external or internal users to an account and assigning resource-level roles to each individual. Assigning the Writer (Developer) role scoped to the specific watsonx Assistant instance gives each developer the access they need without sharing credentials. Individual user identities also appear in Activity Tracker audit events, satisfying the accountability requirement. Shared credentials and shared API keys eliminate auditability. The correct answer, "Invite each developer to the IBM Cloud account as an individual user and assign each person the appropriate IAM role (e.g., Writer) scoped to the watsonx Assistant resource", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Create a single IBM Cloud account with one set of credentials and distribute the username and password to all five developers", "Generate five separate API keys from a single service account and assign them to each developer", "Create a separate watsonx Assistant service instance for each developer to ensure complete isolation") may appear relevant but each misses a key requirement or introduces a step that is either unnecessary or belongs to a different workflow. Mastering the distinction between these approaches is essential for effective watsonx Assistant implementations and is a core focus of the Domain 5: Administration section of the certification exam.