Explanation:

The Definition of Done (DoD) is a shared, formal checklist of criteria that a product increment must meet for it to be considered complete and potentially shippable. It is a cornerstone of quality assurance in Agile.

In this scenario, the code may be functionally correct (passing UAT), but it fails non-functional requirements that are part of the team's DoD, such as:

- Adherence to coding standards
- Maintainability
- Performance benchmarks

Because these criteria are not met, the work is not truly "Done," and the principle of the DoD is violated. The BA is correct to block deployment until the DoD is fully satisfied.

Analysis of Other Options:
A. Sprint retrospective: The retrospective is a ceremony held after a sprint to discuss what went well and what could be improved. While the discovery of this issue would certainly be a topic for the next retrospective, the problem itself is a violation of the "Definition of Done," not the retrospective.

C. Iterative development: Iterative development is the core Agile practice of building software in small, repeating cycles. This scenario does not violate that principle; in fact, discovering this issue before deployment is a benefit of the iterative process and continuous integration. The problem is that the output of one of those iterations did not meet the team's quality bar (the DoD).

Reference:
This is a fundamental Agile principle. The "Definition of Done" ensures a consistent level of quality and completeness across all user stories. It often includes criteria from development (code reviewed, meets standards), testing (UAT passed), and product (acceptance criteria met). A story is not considered finished just because it works; it must also be well-built.

Explanation:

When a project includes multiple stakeholders with different priorities, viewpoints, and interests, it is common to experience misalignment, conflict, and unclear direction. The best response is to establish collaboration norms and shared ownership, which is done through a team agreement (sometimes called a working agreement).

A strong team agreement helps by:
- Defining roles and responsibilities
- Clarifying decision-making methods
- Establishing expectations for communication and conflict resolution
- Aligning on definition of success
- Increasing trust and psychological safety

This creates a healthy foundation for productive discovery, solutioning, and decision-making.

Why not A or B?
A. Encourage leadership to share vision & limit feedback focus
Leadership direction is important, but top-down control alone does not resolve stakeholder conflict or promote shared accountability.
This may reduce engagement from non-leaders and doesn’t fix collaboration issues.

B. Limit participation to leadership only
This excludes valuable perspectives, increases risk of missed requirements, and can lead to poor adoption.
Also reduces transparency and team buy-in.

Conclusion
To ensure collaboration, clarity, and shared success, the BA should create a team agreement.

➡️ Correct answer: C

Explanation:

In Salesforce, each User can be assigned only one Profile. The Profile determines:
- Object-level and field-level permissions
- App and tab visibility
- Record types and page layouts
- Login hours and IP restrictions

This is a core security and access control mechanism in Salesforce. If a user needs additional permissions beyond their Profile, you can use Permission Sets — which can be assigned in multiples.

❌ Why not the others?
A. Up to 3 ❌ Incorrect — Salesforce does not support multiple Profiles per user.
B. Admins up to 3, normal users only 1 ❌ Incorrect — all users, including Admins, are limited to one Profile.
C. As many as required ❌ Incorrect — only Permission Sets can be assigned in multiples, not Profiles.

📚 Reference:
- Salesforce Help: Profiles Overview
- Trailhead: User Management

Explanation:

The initial discovery meeting is primarily focused on understanding the business problem, pain points, and opportunities for improvement.

Limitations of the current support process (the "As-Is" state, including its pain points, bottlenecks, and manual steps) directly reveal:
- The Business Need: Why the project is necessary in the first place.
- Scope and Value: What the new solution must fix, which helps define the scope and estimate the potential value (ROI) of the project.
- Future Requirements: Understanding what doesn't work now is the foundation for defining the requirements for the "To-Be" (future) process.

This information is essential for validating the project's purpose and ensuring the future solution addresses the most critical business issues.

❌ Incorrect Answers
A. Employee review cycle for the support team: This relates to Human Resources and performance management. While it might provide context on team morale or motivation, it is too granular and peripheral to the initial discovery meeting, which focuses on process and system functionality.

C. Contact information for key stakeholders: Important for ongoing project management, but gathering it is an administrative task documented as part of meeting preparation or minutes. It is necessary, but not the core business information defining the project's scope and requirements.

📚 References
- Business Analysis Body of Knowledge (BABOK® Guide): Initial analysis tasks involve understanding the Current State and identifying the Business Need or Problem by examining limitations, pain points, and challenges of the existing process.
- Salesforce Certified Business Analyst Exam Guide: The "Process Mapping and Analysis" domain emphasizes conducting a current state assessment to identify friction points and areas for improvement.

Explanation:

When an Admin creates a new user in Salesforce (Setup → Users → New User), there is a specific checkbox at the bottom of the user creation screen that controls password generation and notification.

Why C (Select "Generate Passwords and notify the user via email") is Correct:
Checking this box (wording: "Generate new password and notify user immediately" in Lightning Experience or "Generate Passwords and notify the user via email" in Classic) does two things:
- Salesforce automatically generates a temporary, system-created password
- Sends the new user an email with a set password link that expires in a limited time (default 7 days, configurable)
This is the standard and only way to force a temporary password instead of manually entering a permanent one.

Why A (Select "Temporary Password and Confirmation Email Required") is Not Correct:
No such checkbox or option exists in Salesforce.

Why B (There are no temporary passwords available…) is Not Correct:
False—Salesforce generates temporary passwords when the “Generate new password and notify” option is selected.

Why D (This is a default feature, no setup required) is Not Correct:
By default, the checkbox is unchecked. If not selected, the Admin must manually type a permanent password. Temporary password behavior is opt-in, not automatic.

Reference:
- Salesforce Help: Create New Users – “Select Generate new password and notify user immediately to send the user a temporary login password.”
- Trailhead: Manage Users – Confirms the checkbox is required for temporary password generation.