Correct Answers: A, C and D
When Solution Architects collect and review the requirements, they should always consider the feasibility of meeting the requirement. It could include the feasibility of the requirement for a new or current feature. It would be best to verify that users use the feature or that the feature is required and will be used. Or you need to verify that implementation of some requirements would not violate rules, regulations, or laws. If the requirements are in violation, you must remove them from the project scope. Also, it is very important to assess the technology limitations or performance expectations. The performance requirements must be based on the target infrastructure or software defined for the project to run. If the expectations for the performance are above the defined technology capabilities, you need to communicate with a customer and change or remove the requirement. Option B is incorrect because the proof of concept is essential for the pre-sales stage and initial design stage, but it is not part of the requirements. It can be used to prove or test the feasibility of the requirements.
Option E is incorrect because the naming convention for the project is an important tool for smooth solution implementation and maintenance. But the convention is not a typical project requirement that needs to be assessed on feasibility.
For more information about the assessment of the feasibility of the requirements, please visit the below URL:
https://docs.microsoft.com/en-us/learn/modules/fit-gap-analysis/2-feasibility