Microsoft and any contributors grant you a license to the Microsoft documentation and other content This project has adopted the Microsoft Open Source Code of Conduct.įor more information see the Code of Conduct FAQ orĬontact with any additional questions or comments. You will only need to do this once across all repos using our CLA. When you submit a pull request, a CLA bot will automatically determine whether you need to provideĪ CLA and decorate the PR appropriately (e.g., status check, comment). Most contributions require you to agree to aĬontributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us This project welcomes contributions and suggestions. Technical Requirements - Resiliency, HA/BC/DR, Observability, Scaling.
Software Development Life Cycle (SDLC) - DevOps, Environments.Project - Design/Operations Team, Success Criteria.Business Context - Customer type, Industry, Licensing, etc.Architecture - Software Architecture of the solution.To start, it's recommended to investigate each of the domains at a high level and then dig deeper as the conversation warrants.
#SOLUTIONS ARCHITECT INTERVIEW QUESTIONS HOW TO#
How to useĮach top-level Domain is broken up into a separate page which covers that domain and its relevant subdomains. These pages are designed to help cover all bases during the investigation stage of a project. IntentĪs a Cloud Solution Architect, we need to be able to quickly vet and understand a wide range of solutions before starting the discussing implementation. This repository is a checklist of questions to ask yourself and your customer when designing a new cloud solution architecture or migrating an existing archtiecture to the cloud.
0 kommentar(er)
