The answer is to use an Azure Policy definition with a 'pattern' constraint on the 'name' field. This is correct because the 'pattern' constraint leverages regular expressions to enforce complex naming conventions, such as requiring resource groups to start with 'prod-', followed by a three-letter department code and a two-digit number—a rule precisely captured by a regex like '^prod-[a-z]{3}\d{2}$'. On the Microsoft Azure Solutions Architect Expert AZ-305 exam, this tests your ability to select the appropriate constraint type for governance scenarios involving multi-part naming rules, where simple wildcards or prefixes fall short. A common trap is confusing 'pattern' with 'like' constraints; remember that 'like' supports only basic wildcards (* and ?), while 'pattern' handles the full regex logic needed for structured codes. For a quick memory tip: think "Pattern = Regex Power" when you see multi-segment naming rules.
AZ-305 Practice Question: Design identity, governance, and monitoring solutions
This AZ-305 practice question tests your understanding of design identity, governance, and monitoring solutions. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are designing a governance strategy for a multi-subscription Azure environment. Your compliance team requires that any resource group created in the production subscription must have a specific naming convention: it must start with 'prod-' and be followed by a three-letter department code and a two-digit number. Any resource group not following this convention should be automatically prevented from creation. Which Azure policy definition should you use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a policy with 'pattern' constraint on the 'name' field.
Option D is correct because Azure Policy's 'pattern' constraint uses regular expressions to enforce complex naming conventions. The requirement for resource groups to start with 'prod-', followed by a three-letter department code and a two-digit number, is a pattern that can be precisely defined with a regex like '^prod-[a-z]{3}\d{2}$'. The 'pattern' constraint is the only option that supports regex-based validation, making it suitable for this multi-part naming rule.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use a policy with 'like' constraint on the 'name' field.
Why it's wrong here
'like' uses simple wildcards and cannot enforce exact pattern with regex.
✗
Use a policy with 'match' constraint on the 'name' field.
Why it's wrong here
'match' is not a valid constraint in Azure Policy.
✗
Use a policy with 'contains' constraint on the 'name' field.
Why it's wrong here
'contains' only checks if a substring exists, not pattern matching.
✓
Use a policy with 'pattern' constraint on the 'name' field.
Why this is correct
The 'pattern' constraint supports regex, allowing validation of the naming convention.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'match' (which uses simple wildcards like '*' and '?') with 'pattern' (which uses regex), leading them to choose option B when the requirement demands a structured format that only regex can enforce.
Detailed technical explanation
How to think about this question
Azure Policy's 'pattern' constraint leverages .NET regular expressions under the hood, allowing for complex validations like '^prod-[a-z]{3}\d{2}$'. This regex ensures the name starts with 'prod-', followed by exactly three lowercase letters (department code), and ends with exactly two digits. In a real-world scenario, you would also need to consider case sensitivity and apply the policy at the subscription scope to prevent non-compliant resource group creation entirely.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-305 question in full detail.
Design identity, governance, and monitoring solutions — This question tests Design identity, governance, and monitoring solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a policy with 'pattern' constraint on the 'name' field. — Option D is correct because Azure Policy's 'pattern' constraint uses regular expressions to enforce complex naming conventions. The requirement for resource groups to start with 'prod-', followed by a three-letter department code and a two-digit number, is a pattern that can be precisely defined with a regex like '^prod-[a-z]{3}\d{2}$'. The 'pattern' constraint is the only option that supports regex-based validation, making it suitable for this multi-part naming rule.
What should I do if I get this AZ-305 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-305 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-305 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.