Setting Up Procurement Category Hierarchy by Country

MB-330 By islever Editorial Last updated

Short answer

B Create category hierarchy nodes per each country underneath the consolidated legal entity to group purchase requisition items by country as required by policy.

Question

You need to set up the procurement category hierarchy in accordance with company policy.
What should you do?
  1. Add four nodes to the category hierarchy, one for US, one for Hungary, one for California, and one for Colorado.
  2. Create category hierarchy nodes per each country underneath the consolidated legal entity. Correct Answer
  3. Add three nodes to the category hierarchy, one for Hungary, one for California, and one for Colorado.
  4. Create a procurement category hierarchy and assign purchase policy per legal entity only.

Key Takeaways

This question tests your ability to map organizational governance rules (country-based) to the structural hierarchy of procurement categories, avoiding the trap of over-segmenting by sub-national regions like states.

Learn how to configure a procurement category hierarchy in Dynamics 365 Supply Chain Management when governance is required by country. The correct setup involves creating nodes per country under the legal entity.

Common mistake: Many candidates choose Option A, incorrectly creating separate nodes for US states (California, Colorado) alongside countries. This fails because the governance rule is specifically tied to the country level, requiring states to be grouped under their respective country nodes rather than standing alone.

Expert Analysis

The question requires setting up a procurement category hierarchy based on specific company policies. The key constraint, derived from the case study context referenced in the comments, is that "Items for purchase requisitions are governed by each country." This means the hierarchy must reflect national boundaries to ensure proper grouping and governance of purchasing activities.

Option B is the correct approach because it creates nodes per country (US and Hungary) under the consolidated legal entity. This structure aligns with the requirement that items be grouped and governed by country. It correctly identifies the two distinct countries involved in the scenario.

Option A is the most attractive but incorrect answer. It includes four nodes: US, Hungary, California, and Colorado. While it captures all geographic entities mentioned, it fails to group California and Colorado under the US node. Since the governance rule is based on country, not state/province, separating US states into their own top-level categories violates the principle of grouping by country. Option C is similarly flawed as it mixes states with a country without a hierarchical parent-child relationship that reflects the country-based governance. Option D suggests assigning policies per legal entity only, which ignores the explicit requirement for country-specific governance.

The core trap here is confusing geographic granularity. Candidates might think they need separate nodes for every location, but the policy dictates grouping by country. Therefore, states should be subordinate to their respective country nodes or excluded if not relevant to the category structure's primary governance level.

Exam Strategy

When configuring hierarchies in supply chain scenarios, always identify the primary 'governance' or 'grouping' dimension stated in the requirements (e.g., country, division, brand). Build the top-level nodes around that dimension. If sub-regions (like states) are mentioned, check if they require separate governance; if not, they should likely be nested under the primary dimension or ignored in the high-level hierarchy design.

Frequently Asked Questions

Why not create separate nodes for US states?

Because the policy requires items to be governed by country. Creating separate nodes for states breaks the country-based grouping logic intended by the policy.

Can I assign purchase policies per legal entity instead?

No, the scenario explicitly states that purchase requisition items are governed by each country, so the hierarchy must reflect this country-level distinction.

More MB-330 FAQ →

Community Votes

B
50%
D
50%

50% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 5 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 5

  1. mondays 👍 2
    Requirement: Items for purchase requisitions are governed by each country. Each of the country-specific products will be grouped together for selection Sounds like Proc categories? Create category hierarchy nodes per each country underneath the consolidated legal entity
  2. Gemami 👍 1 Answered B
    Correct answer: B. Create category hierarchy nodes per country. Why B? Purchase requisition items must be grouped and governed by country (US and Hungary). Why not others? - A: Incorrectly separates California and Colorado instead of grouping them under the US. - C: Mixes states (California, Colorado) with a country (Hungary). - D: Purchase policies control purchasing rules but don't establish country-specific product categories.
  3. H_Incandenza 👍 1
    Granted I'm only skimming, but it isn't clear to me why they need either the procurement categories or the purchasing policies. The only thing that remotely stands out is that they are using a purchase requisition workflow, which perhaps could require policy rules. But to me, there's not enough detail such that any one policy rule jumps off the page as required.
  4. globeearth 👍 1 Answered D
    Requirement case-study has 2 points- 1. Items for purchase requisitions are governed by each country. Each of the country-specific products will be grouped together for selection.2. It has company policy. Only option D suits the country wise approach and enforcing policies.
  5. mondays 👍 1
    could also be D :(

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

← Back to MB-330 Study Guide