Your question is Risk-Based Testing Strategy. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You are planning QA for a product release with limited time and test capacity, so you cannot test every workflow with the same depth. You need a practical way to focus effort on the areas most likely to cause business, customer, or operational impact while still giving stakeholders confidence in the release.
What strategies do you use for risk-based testing?