MB-230 · Question #371
Drag and Drop Question A company that operates in 101 countries/regions globally uses Dynamics 365 Customer Service. The countries/regions currently use the same environment. An administrator plans th
The correct answer is 3; 3; 101. Explanation: Dynamics 365 Portal Environment Requirements Core Rule to Understand Microsoft enforces a one portal per environment constraint. This single rule drives all three answers. --- Placement 1: Dataverse Starter Portal → 3 Technical reason: A Dataverse starter portal only
Question
Drag and Drop Question A company that operates in 101 countries/regions globally uses Dynamics 365 Customer Service. The countries/regions currently use the same environment. An administrator plans the deployment of additional portals to support customer service processes. Each country/region requires the following:
- A Microsoft Dataverse starter portal in an environment with Dataverse
- A blank portal in an environment with customer engagement apps
- A pre-built portal in an environment with customer engagement apps
You need to determine the minimum number of environments required. How many environments will you need? To answer, drag the appropriate number to the portal requirements. Each number of may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:
Exhibit
Answer Area
Drag items
Correct arrangement
- 3
- 3
- 101
Explanation
Explanation: Dynamics 365 Portal Environment Requirements
Core Rule to Understand
Microsoft enforces a one portal per environment constraint. This single rule drives all three answers.
Placement 1: Dataverse Starter Portal → 3
Technical reason: A Dataverse starter portal only requires an environment with Dataverse (no Customer Engagement apps needed). This portal type is "generic" - it can be configured to serve multiple countries/regions from a single shared environment. You do not need one per country.
The minimum of 3 follows Microsoft's standard deployment model:
- 1 Development environment
- 1 Test/UAT environment
- 1 Production environment
All 101 countries share the single production portal.
Placement 2: Blank Portal → 3
Technical reason: Same reasoning as above. A blank portal (in a CE app environment) has no pre-built country-specific content. It can be shared globally across all 101 countries from one production environment.
Again, 3 environments = dev + test + prod. The blank portal's generic, customizable nature means you don't need per-country isolation.
Placement 3: Pre-built Portal → 101
Technical reason: This is the critical distinction. Pre-built portals (e.g., Customer Self-Service, Partner Portal) are tightly coupled to the Dynamics 365 CE organization data within their environment. Each country's CE environment contains its own data, customizations, and business logic.
Because each country has a separate CE app environment - and because you can only have one portal per environment - you need exactly 1 environment per country = 101 environments.
Common Mistakes
| Mistake | Why it's wrong |
|---|---|
| Answering 101 for all three | Only pre-built portals require per-country environments; the other two types can be shared globally |
| Answering 1 for starter/blank portals | Ignores the dev/test/prod minimum deployment model |
| Answering 50 for any slot | The "50" is a distractor; it has no basis in portal provisioning rules |
| Treating blank and pre-built portals the same | The key distinction is that pre-built portals are bound to specific CE org data; blank portals are not |
The Core Distinction
Shared portals (Dataverse starter, blank) → configurable for any country from one environment → 3 minimum Data-bound portals (pre-built) → locked to a specific CE org → must be 1 per country → 101
Topics
Community Discussion
No community discussion yet for this question.