When a business analyst finds it difficult to get a response from a subject matter expert (SME), they should escalate the concern to the SMEs' manager. This is because the SMEs' manager can help to prioritize the project, provide feedback, and ensure accountability. The business analyst should also document the communication attempts and issues, and keep the project sponsor and other stakeholders informed of the status and risks. References: https://trailhead.salesforce.com/content/learn/modules/salesforce-business- analyst-certification-prep/collaboration-with-stakeholders

Explanation
The level of detail that the business analyst should use for the process map and why is somewhat detailed.
This is because the process map should provide enough information to guide new users through the onboarding process, but not overwhelm them with too much detail that may be irrelevant or unnecessary.
Since the process will be repetitive, new users will learn and remember the details over time, and they can always refer back to the process map if needed. The process map should include the main steps, decisions, inputs, outputs, and roles involved in the onboarding process, as well as any exceptions or variations. The process map should also use clear and consistent terminology, symbols, and notation to ensure readability and understanding. References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/business-pro

The business analyst should use a stakeholder analysis to gather additional perspective, feedback, and detail on the requirements from the NTO team. A stakeholder analysis is a technique to identify and understand the needs, expectations, interests, influence, and power of the stakeholders involved in a project. A stakeholder analysis can help the business analyst communicate effectively with the stakeholders, manage their expectations, address their concerns, involve them in decision making, and obtain their feedback and approval. A business analysis plan is not a document to gather additional perspective, feedback, and detail on the requirements from the NTO team. A business analysis plan is a document that describes how the business analysis activities will be conducted, such as what techniques, tools, deliverables, roles, and responsibilities will be used. A business analysis plan can help the business analyst plan and manage their work, but it does not help them gather information from the stakeholders. A current state analysis is not a document to gather additional perspective, feedback, and detail on the requirements from the NTO team. A current state analysis is a technique to understand and document how the current situation or process works, what are its strengths and weaknesses, what are the problems or opportunities for improvement, and what are the root causes of the issues. A current state analysis can help the business analyst identify gaps and needs, but it does not help them gather information from the stakeholders. References: https://trailhead.salesforce.com/en/content/learn
/modules/business-analyst_skills-strategies/explore-techniques-information-discovery

Explanation
The items that the business analyst documented are non-functional requirements. Non-functional requirements are statements that describe how a system or solution should perform, behave, or appear, rather than what it should do or provide. Non-functional requirements can include aspects such as usability, reliability, security, availability, scalability, etc. Non-functional requirements help to ensure that the system or solution meets the quality standards and expectations of the stakeholders or users. The items that the business analyst documented are non-functional requirements because they specify how Sales Cloud should perform (portal pages should load within 2 seconds) and behave (all logins must use multi-factor authentication).
References:https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/