I85PREP
⌘ K
HCSP-Cloud Migration study materials
HCSP-Cloud Migration study resources

HCSP-Cloud Migration practice questions

One question at a time. Build your HCSP-Cloud Migration understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Cloud Migration Overview and Methodology

In a cloud migration methodology, what is the primary purpose of a discovery and assessment phase?

  1. To decommission legacy systems as quickly as possible to reduce cost
  2. To provision the target cloud accounts before any workload analysis begins
  3. To inventory existing workloads and dependencies so migration decisions are based on evidence Correct answer.
  4. To negotiate vendor contracts for the target platform

Explanation

Discovery and assessment builds the factual baseline for a migration: what applications exist, how they communicate, their data volumes, and their business criticality. Without this inventory, later decisions about migration strategy, sequencing, and cost become guesswork. Provisioning, decommissioning, and contracting happen after or alongside the assessment, not as its purpose.

Question 2Cloud Migration Overview and Methodology

Which migration strategy keeps an application essentially unchanged but moves it to cloud infrastructure?

  1. Refactor
  2. Rehost Correct answer.
  3. Retire
  4. Repurchase

Explanation

Rehost, often called lift-and-shift, moves a workload to cloud infrastructure with minimal code change. It is usually the fastest path and is often used to exit a data center on a deadline before later optimization. Refactor changes the architecture, retire removes the application, and repurchase replaces it with a SaaS product.

Question 3Cloud Migration Overview and Methodology

A team wants to move a legacy reporting application to SaaS to eliminate its maintenance burden. Which migration strategy does this describe?

  1. Relocate
  2. Replatform
  3. Repurchase Correct answer.
  4. Retain

Explanation

Repurchase means replacing the existing application with a different product, commonly a SaaS offering, and migrating data and users to it. The driver here is eliminating maintenance of a legacy system, which fits repurchase. Replatform would keep the same application while adjusting its runtime, retain would leave it in place, and relocate would move it without changing the product.

Question 4Cloud Migration Overview and Methodology

What distinguishes a migration wave from a single application migration?

  1. A wave is a synonym for one application moved in isolation
  2. A wave groups workloads released together on a shared schedule and dependency plan Correct answer.
  3. A wave is a billing construct that aggregates cloud spend
  4. A wave is the network bandwidth allocated during cutover

Explanation

Waves are the unit of planning and execution in large migrations: a set of applications that share dependencies, owners, and a cutover window and are moved together. Grouping into waves lets teams sequence work and manage risk instead of treating each application as an isolated event. Bandwidth and billing are unrelated concepts.

Question 5Cloud Migration Overview and Methodology

Which statement best describes the role of a business case in a cloud migration program?

  1. It quantifies expected benefits and costs to justify and steer the migration investment Correct answer.
  2. It documents the source code changes made during refactoring
  3. It replaces the technical discovery inventory with financial estimates
  4. It is only required after all workloads have already been migrated

Explanation

A business case compares projected costs, such as run rate, migration effort, and licensing, against expected benefits like agility, resilience, and avoided data center spend. It guides investment decisions and later helps validate whether realized outcomes match projections. It complements rather than replaces technical discovery.

Question 6Cloud Migration Overview and Methodology

What is the main purpose of a cloud center of excellence during a migration program?

  1. To take over all application migrations from delivery teams
  2. To approve individual employee expense reports
  3. To procure hardware for the source data center
  4. To define standards, guardrails, and reusable patterns that migration teams adopt Correct answer.

Explanation

A center of excellence provides shared standards, reference architectures, landing zone patterns, and guidance so that many teams migrate consistently. It enables teams rather than replacing them, and it reduces duplicated effort across waves. Hardware procurement and expense approval are unrelated administrative functions.

Question 7Cloud Migration Overview and Methodology

Which activity belongs in the operate phase rather than the migrate phase of a cloud adoption lifecycle?

  1. Continuous cost optimization and incident response for workloads already in production Correct answer.
  2. Definition of the target landing zone architecture
  3. Pilot migration of a first low-risk workload
  4. Detailed application dependency mapping before cutover

Explanation

The operate phase covers running workloads after migration: monitoring, incident response, patching, and ongoing cost and performance optimization. Dependency mapping, pilot migrations, and landing zone design are preparation and migration activities that precede steady-state operations. Confusing these phases leads to understaffed operations and surprise costs.

Question 8Cloud Migration Overview and Methodology

What does a landing zone provide in a cloud migration program?

  1. A list of applications approved for retirement
  2. A contractual agreement with the cloud provider
  3. A temporary staging server used only for data transfer
  4. A pre-configured, governed baseline environment into which workloads are deployed Correct answer.

Explanation

A landing zone is the prepared foundation of the target environment: accounts, networking, identity, logging, security controls, and guardrails. Workloads are deployed into it so that compliance and connectivity requirements are met consistently from day one. It is not a single transfer server or a commercial contract.

Question 9Cloud Migration Overview and Methodology

A migration team must move a stateful database with a strict four-hour cutover window. Which planning element most directly reduces cutover risk?

  1. Deferring dependency mapping until after cutover
  2. Rehearsing the cutover runbook with rollback steps in a test environment Correct answer.
  3. Increasing the number of applications assigned to the same wave
  4. Choosing the strategy with the largest code rewrite

Explanation

A tight cutover window is best managed by rehearsing the runbook, including validation checks and a tested rollback path, so the team knows the timing and failure modes in advance. Adding applications to the wave increases risk rather than reducing it. Dependency mapping and strategy selection must be settled before cutover, not deferred or decided by rewrite size.

Question 10Cloud Migration Overview and Methodology

During assessment, a team finds an application with no owner, no active users, and duplicated functionality in a newer system. Which strategy is most appropriate?

  1. Relocate
  2. Retire Correct answer.
  3. Rehost
  4. Replatform

Explanation

An application with no owner, no users, and duplicate functionality is a retirement candidate; migrating it would carry cost and risk for no benefit. Retiring it also simplifies the portfolio before other workloads move. Rehost, replatform, and relocate all assume the application should continue running in some form.

Question 11Cloud Migration Overview and Methodology

What is the key difference between replatform and refactor as migration strategies?

  1. Replatform makes targeted changes to the runtime or platform, while refactor re-architects the application Correct answer.
  2. Replatform replaces the application with SaaS, while refactor keeps it on premises
  3. Replatform rewrites the application code entirely, while refactor only changes the hosting region
  4. Replatform retires the application, while refactor keeps it unchanged

Explanation

Replatform, sometimes called lift-tinker-and-shift, keeps the application largely intact while adjusting managed services, runtime versions, or configuration to gain cloud benefits. Refactor involves deeper architectural change, such as decomposing a monolith into services, to gain scalability and agility. The two differ in depth of change, not in hosting region or retirement.

Question 12Cloud Migration Overview and Methodology

Why is application dependency mapping critical before defining migration waves?

  1. It reveals which applications must move together to avoid broken integrations Correct answer.
  2. It replaces the need for a rollback plan during cutover
  3. It determines the cloud provider's published pricing tiers
  4. It guarantees that every application will be refactored

Explanation

Dependency mapping shows network calls, shared databases, authentication flows, and batch interfaces between applications. Those relationships determine which workloads must be grouped in the same wave or cut over in a defined order. Pricing tiers, rollback planning, and refactoring decisions are separate concerns that mapping informs but does not replace.

Question 13Cloud Migration Overview and Methodology

A migration program defines success only as reducing data center square footage. Which risk does this create?

  1. Workloads may be migrated without validating performance, security, or business outcomes Correct answer.
  2. Applications will be retired too slowly
  3. The program will automatically exceed its budget
  4. The landing zone will be over-engineered

Explanation

Measuring success only by data center exit rewards speed of relocation and can leave performance, security posture, and user experience unvalidated. Good programs pair exit metrics with outcome metrics such as availability, latency, cost per transaction, and compliance. The other options are not logical consequences of a square-footage metric.

Question 14Cloud Migration Overview and Methodology

Which approach best supports migrating a large portfolio of similar applications efficiently?

  1. Industrializing the pattern with automated templates and a repeatable factory process Correct answer.
  2. Treating every application as a unique bespoke project
  3. Migrating all applications simultaneously in one wave
  4. Postponing all automation until the final wave

Explanation

When many applications share similar characteristics, a factory approach with automated provisioning, standard runbooks, and reusable templates reduces per-application effort and error rates. Bespoke projects and a single massive wave both increase cost and risk. Automation delivers its benefit only if applied early and repeatedly.

Question 15Cloud Migration Overview and Methodology

What is the purpose of a pilot migration in a cloud migration methodology?

  1. To validate the approach, tooling, and landing zone on a limited scope before scaling Correct answer.
  2. To permanently host a small subset of applications outside the main program
  3. To satisfy an audit requirement for all production workloads
  4. To move the most business-critical system first to prove capability

Explanation

A pilot uses a small, representative, low-to-moderate risk workload to test the landing zone, migration tooling, runbooks, and team readiness. Lessons learned are then applied at scale. Starting with the most critical system amplifies risk, and a pilot is a validation step rather than a permanent separate hosting arrangement.

Question 16Cloud Migration Overview and Methodology

Which factor most strongly argues for choosing refactor over rehost for a particular application?

  1. The application is a commercial product with a supported SaaS equivalent
  2. The application must scale elastically and its monolith blocks frequent releases Correct answer.
  3. The application has only six months before its data center lease expires
  4. The application has no active development team

Explanation

Refactoring is justified when architectural change unlocks business value, such as elastic scaling or faster release cycles that the current design prevents. A short lease deadline favors rehost for speed, an unmaintained application may be a retire candidate, and a SaaS equivalent points to repurchase.

Question 17Cloud Migration Overview and Methodology

What does a migration readiness assessment typically evaluate?

  1. Only the licensing terms of the target cloud provider
  2. Only the number of servers in the source data center
  3. Organizational skills, governance, security posture, and process maturity for cloud adoption Correct answer.
  4. Only the source code line count of each application

Explanation

A readiness assessment examines whether people, processes, governance, and security controls can support cloud operations, not just technical inventory. Gaps identified become part of the program's enablement and remediation plan. Counting servers, license terms, or code lines alone gives a narrow and misleading picture.

Question 18Cloud Migration Overview and Methodology

A regulated bank wants to migrate workloads but must keep data residency and audit evidence intact. Which planning artifact should be established first?

  1. A marketing plan for the new cloud platform
  2. A refactoring backlog for every application in the portfolio
  3. A single wave containing all regulated applications
  4. A landing zone with enforced residency, logging, and compliance guardrails Correct answer.

Explanation

Regulatory constraints such as residency and auditability are structural, so the governed landing zone must encode them through region restrictions, centralized logging, and policy controls before workloads arrive. Building this first prevents costly rework and noncompliance. Refactoring backlogs, marketing plans, and a single mega-wave do not establish compliance controls.

Question 19Cloud Migration Overview and Methodology

Which metric best indicates whether a migration program is realizing its intended cloud benefits?

  1. Cost per transaction compared with the pre-migration baseline Correct answer.
  2. Number of migration meetings held per week
  3. Total lines of code changed during migration
  4. Count of vendor invoices received

Explanation

Benefit realization is measured by comparing business-relevant outcomes, such as unit cost, availability, or deployment frequency, against the pre-migration baseline. Process activity metrics like meeting counts and code churn measure effort, not value. Invoice counts say nothing about efficiency or outcomes.

Question 20Cloud Migration Overview and Methodology

What is the main reason to sequence migration waves by business value and risk rather than by application size alone?

  1. Risk disappears once an application is large enough
  2. Business value is unrelated to migration priority
  3. Large applications are always technically impossible to migrate
  4. Sequencing balances early benefit delivery against the risk the organization can absorb Correct answer.

Explanation

Wave sequencing is a trade-off between delivering value early, building momentum, and keeping risk within what teams and the business can tolerate. Size alone ignores criticality, dependencies, and readiness. Large applications are migratable, and risk does not vanish with scale.

Question 21Cloud Migration Overview and Methodology

An organization plans to relocate a VMware-based workload to cloud infrastructure that supports the same hypervisor, keeping operations largely unchanged. Which strategy is this?

  1. Retire
  2. Refactor
  3. Repurchase
  4. Relocate Correct answer.

Explanation

Relocate moves workloads to another infrastructure environment while preserving the platform, such as the same hypervisor and operational tooling, so teams avoid retraining and re-architecting. Refactor and repurchase change the application or product, and retire removes it entirely.

Question 22Cloud Migration Overview and Methodology

Which governance mechanism best prevents teams from deploying workloads that violate organizational security policy in a new cloud environment?

  1. Preventive policy controls enforced in the landing zone Correct answer.
  2. A wiki page describing recommended configurations
  3. A post-incident review after a breach occurs
  4. A monthly reminder email to engineering managers

Explanation

Preventive controls, such as policy-as-code guardrails and organization-level restrictions, block noncompliant deployments before they happen. Reminders, documentation, and after-the-fact reviews rely on voluntary compliance or detect problems only after harm. Effective cloud governance combines preventive and detective controls in the landing zone.

Question 23Cloud Migration Overview and Methodology

A migration program shows rising cloud run costs after several waves. Which analysis best identifies whether the increase reflects expected migration effects or inefficiency?

  1. Compare unit economics and tag-based cost allocation against pre-migration baselines and forecast Correct answer.
  2. Assume all cost growth is temporary and take no action
  3. Move all workloads back to the data center
  4. Cancel the remaining waves until costs fall

Explanation

Distinguishing expected transition costs from waste requires attributing spend to workloads through tagging and comparing unit economics, such as cost per transaction, against baselines and forecasts. Growth may reflect duplicated running during transition or genuine inefficiency. Ignoring it, halting waves, or reversing the migration are disproportionate responses without evidence.

Question 24Cloud Migration Overview and Methodology

Why should a migration methodology treat data migration and application migration as coordinated but separately planned workstreams?

  1. Application code and data always migrate at exactly the same moment with no sequencing
  2. Application migration cannot begin until all data is permanently deleted
  3. Data has its own integrity, volume, and synchronization requirements that constrain cutover sequencing Correct answer.
  4. Data migration never requires validation after transfer

Explanation

Data migration involves volume, integrity checks, transformation, and often ongoing synchronization between source and target until cutover. These constraints interact with application cutover order but require distinct planning, tooling, and validation. Treating them as one undifferentiated task hides the riskiest part of many migrations.

Question 25Cloud Migration Overview and Methodology

A team proposes skipping the assessment phase because the deadline is tight and the portfolio is 'well understood.' Which consequence is most likely?

  1. The landing zone automatically discovers and resolves all dependencies
  2. Hidden dependencies and licensing constraints surface late, causing cutover failures and rework Correct answer.
  3. The migration completes faster with no additional risk
  4. Costs decrease because assessment effort is eliminated

Explanation

Assessment surfaces dependencies, licensing obligations, data volumes, and integration constraints that institutional knowledge typically misses. Compressing it shifts discovery into execution, where surprises cause failed cutovers and expensive rework. No landing zone automatically resolves unknown dependencies, and skipped effort is deferred rather than eliminated.

Question 26Cloud Migration Overview and Methodology

In a cloud migration methodology, what distinguishes the discovery step from the assessment step?

  1. Discovery inventories what exists and how it connects, while assessment judges each workload's suitability, risk, and target strategy. Correct answer.
  2. Discovery is performed after cutover, while assessment is performed before any workload is touched.
  3. Discovery decides the final migration wave order, while assessment only records the technical attributes of each server.
  4. Discovery produces the business case and cost model, while assessment produces the network topology diagram.

Explanation

Discovery is an evidence-gathering step: it builds the portfolio inventory, captures configuration, and maps dependencies between workloads. Assessment consumes that evidence to evaluate business criticality, technical fit, risk, and the preferred migration strategy for each application. Keeping the two steps distinct prevents teams from committing to a strategy before they understand what they actually run.

Question 27Cloud Migration Overview and Methodology

Which statement correctly describes the relationship between a migration strategy and a migration pattern in cloud migration planning?

  1. A strategy is chosen once per program, while a pattern is chosen once per data center.
  2. A strategy is the business intent for a workload, while a pattern is the reusable technical implementation used to achieve it. Correct answer.
  3. A strategy applies only to infrastructure, while a pattern applies only to application source code changes.
  4. A strategy is a vendor contract term, while a pattern is an internal staffing model.

Explanation

Strategies such as rehost, replatform, refactor, retire, and retain express what the organization intends to do with a workload and why. Patterns are the repeatable technical recipes, such as lift-and-shift with replication tooling or containerization with managed services, that implement the chosen strategy consistently across many applications. Separating intent from implementation lets a program standardize execution without forcing one technical approach on every workload.

Question 28Cloud Migration Overview and Methodology

A migration program's steering committee wants a single decision record for each application that states the chosen strategy, the rationale, the owner, and the target date. Which artifact should the methodology require?

  1. A vendor scorecard comparing public cloud providers
  2. A post-migration user satisfaction survey
  3. A per-application migration decision record approved by the accountable owner Correct answer.
  4. A consolidated network latency baseline for the whole portfolio

Explanation

A decision record per application captures the strategy, the reasoning, the accountable owner, and the planned timing, which gives the steering committee an auditable trail and prevents silent strategy drift. It also makes trade-offs explicit so later reviewers can see why rehost was chosen over replatform for a given workload. Portfolio-wide baselines, vendor comparisons, and satisfaction surveys inform decisions but do not record them per application.

Question 29Cloud Migration Overview and Methodology

A program office wants migration waves to be repeatable across regions. Which methodology element most directly enables repeatability while still allowing justified exceptions?

  1. A schedule that fixes wave dates before discovery is complete
  2. A rule that every application must use the same migration strategy regardless of its characteristics
  3. An escalation path that routes all technical issues directly to the steering committee
  4. A standard wave playbook with defined entry and exit criteria plus a documented exception process Correct answer.

Explanation

A playbook with explicit entry and exit criteria gives every wave the same checks for readiness, cutover, and validation, which is what makes results comparable across regions. Pairing it with a documented exception process preserves consistency while letting teams handle workloads that genuinely do not fit the standard. Repeatability comes from standardized gates, not from forcing identical technical choices.

Question 30Cloud Migration Overview and Methodology

Midway through a program, a team reports that several applications marked for retirement are still receiving maintenance spend, and one retired application still appears in the dependency map feeding wave planning. Which methodology weakness does this most directly indicate?

  1. The benefits model counted cost avoidance before the applications were decommissioned
  2. The cutover runbooks omitted a rollback step for the retired workloads
  3. The portfolio baseline lacks a controlled change process that keeps retirement status and dependency data synchronized Correct answer.
  4. The assessment phase used the wrong migration strategy for the affected applications

Explanation

When retired applications keep consuming spend and still appear in dependency data, the portfolio baseline has drifted from reality because no controlled process updates status and dependencies as decisions are made. A migration methodology needs retirement to trigger updates to the inventory, dependency map, and wave plan so downstream planning uses current facts. Strategy selection and rollback design are separate concerns that would not cause stale entries to persist.

Question 31Migration Assessment and Planning

During a migration assessment, which activity best establishes the current-state baseline for an application portfolio before any move to cloud is planned?

  1. Rewriting the applications into cloud-native microservices
  2. Documenting each application's dependencies, usage patterns, and infrastructure footprint Correct answer.
  3. Negotiating reserved-instance commitments for the future environment
  4. Selecting the target cloud region and availability zone layout

Explanation

A migration assessment begins with discovery of the existing estate: what each application does, what it depends on, how heavily it is used, and what infrastructure it consumes. This baseline informs every later decision about the six Rs, landing zone sizing, and sequencing. Region selection, commitment purchasing, and refactoring are downstream planning or execution activities that require the baseline first.

Question 32Migration Assessment and Planning

An assessment team classifies a payroll system as a candidate for the 'retire' strategy. Which condition most directly justifies that classification?

  1. The system runs on an operating system that is still vendor-supported
  2. The system's functionality is fully duplicated by another system already in the portfolio Correct answer.
  3. The system has high business criticality and a large active user base
  4. The system has a documented disaster recovery plan in place

Explanation

Retirement is appropriate when an application delivers no unique business value, for example because its functions are already covered elsewhere. High criticality, supported platforms, and existing DR plans are reasons to keep or migrate a system, not to decommission it. Confirming functional duplication is therefore the decisive evidence for retirement.

Question 33Migration Assessment and Planning

What is the primary purpose of building a migration wave plan during the assessment and planning phase?

  1. To sequence application moves into grouped, dependency-aware batches Correct answer.
  2. To assign each application a target landing zone subnet
  3. To define the security controls for the future environment
  4. To calculate the monthly cost of each target cloud service

Explanation

Wave planning groups applications into batches that can be migrated together, ordered so that dependencies and shared infrastructure are handled in a safe sequence. It is a scheduling and sequencing artifact rather than a network, cost, or security design artifact. Those designs are inputs to the wave plan, not its purpose.

Question 34Migration Assessment and Planning

A migration assessment records that an application stores session state in local memory on each server. Why does this detail matter for planning a move to cloud?

  1. It determines the application's software licensing obligations
  2. It affects whether horizontal scaling and load balancing will work without code change Correct answer.
  3. It decides which cloud provider region must be used
  4. It sets the required backup retention period for the database

Explanation

In-memory session state ties a user's session to a specific server instance, which breaks when traffic is distributed across multiple instances or when instances are replaced. This is a well-known migration constraint that may force externalizing session state before or during the move. Licensing, backup retention, and region choice are unrelated to where session data is held.

Question 35Migration Assessment and Planning

Which total cost of ownership comparison is most appropriate when building the business case for a cloud migration?

  1. Comparing only the monthly compute price of the current servers with the target cloud compute price
  2. Comparing the current hardware purchase price with the cloud provider's list price
  3. Comparing the one-time migration cost with the first month of cloud billing
  4. Comparing fully loaded current-state costs with fully loaded future-state costs over a defined period Correct answer.

Explanation

A defensible business case compares fully loaded costs, including facilities, staffing, licensing, support, and refresh cycles, against the fully loaded future state over a comparable time horizon. Narrow comparisons of compute price or hardware list price omit major cost drivers and distort the result. Migration cost is an investment to be amortized, not a stand-in for the future-state run cost.

Question 36Migration Assessment and Planning

In migration assessment terminology, what does a dependency map primarily capture?

  1. The list of staff certifications required to operate the target platform
  2. The contractual penalties for missing migration milestones
  3. The network, data, and service relationships between applications and shared components Correct answer.
  4. The reporting hierarchy of the IT organization that owns each system

Explanation

A dependency map records how applications connect to one another and to shared services such as databases, directories, message queues, and file shares. These relationships drive wave sequencing and cutover risk. Organizational charts, contract terms, and skills inventories are governance and staffing artifacts, not dependency maps.

Question 37Migration Assessment and Planning

A team is assessing a commercial off-the-shelf application whose vendor offers a supported cloud-hosted version. Which migration strategy does this situation most naturally support?

  1. Refactor the application into a custom-built replacement
  2. Repurchase by moving to the vendor's SaaS offering and retiring the self-hosted instance Correct answer.
  3. Rehost the existing binaries onto cloud virtual machines without vendor involvement
  4. Retain the application on premises indefinitely with no review

Explanation

When a vendor provides a supported SaaS equivalent, moving to that offering is the repurchase (or replace) strategy and typically transfers operational burden to the vendor. Rehosting the binaries may violate support terms, and building a custom replacement is far more costly than adopting the vendor's hosted product. Indefinite retention ignores the available improvement.

Question 38Migration Assessment and Planning

Which artifact in a migration assessment most directly supports prioritization by business value and technical complexity?

  1. A network latency trace between on-premises data centers
  2. A vendor contact list for cloud service providers
  3. A portfolio scoring matrix rating each application on value and migration difficulty Correct answer.
  4. A copy of the current disaster recovery runbook

Explanation

A portfolio scoring matrix rates applications against criteria such as business value, technical complexity, risk, and readiness, which allows objective prioritization. Latency traces, vendor lists, and DR runbooks provide supporting data but do not by themselves rank the portfolio. The matrix is the standard prioritization instrument in assessment.

Question 39Migration Assessment and Planning

An assessment finds that a reporting database is read by twelve downstream applications through a fixed connection string. What planning risk does this create for migrating the database?

  1. The reporting queries will automatically become faster
  2. Cutover requires coordinated changes or a stable endpoint for all twelve consumers Correct answer.
  3. The database must be converted to a NoSQL store
  4. The database cannot be backed up in the target environment

Explanation

Many consumers bound to a fixed connection string create a coordination problem: either all consumers change at cutover or the endpoint must remain stable through DNS or a proxy. This is a classic dependency-driven cutover risk. Backup capability, data model choice, and performance outcomes are separate concerns not implied by the fan-in.

Question 40Migration Assessment and Planning

Which approach best validates that an assessed application will function correctly in the target cloud environment before full cutover?

  1. Estimating the application's monthly cloud cost from a pricing calculator
  2. Interviewing the application owner about their migration preferences
  3. Running a pilot migration of the application into a test landing zone and executing regression tests Correct answer.
  4. Reviewing the application's source code for deprecated API calls only

Explanation

A pilot migration into a representative test environment exercises real networking, identity, storage, and runtime behavior, and regression tests confirm functional parity. Static code review catches only some issues, and cost estimates and interviews produce no behavioral evidence. The pilot is the standard validation technique in migration planning.

Question 41Migration Assessment and Planning

A migration assessment shows an application has a hard requirement that data never leaves a specific country. How should this shape the migration plan?

  1. It has no effect because cloud providers replicate data globally by default
  2. It constrains the choice of cloud region and may require in-country services for storage and processing Correct answer.
  3. It requires the application to be retired rather than migrated
  4. It forces the application to be refactored into containers

Explanation

Data residency obligations restrict where data may be stored and processed, which directly limits the eligible regions and sometimes the services available in those regions. Retirement, containerization, and default global replication are not consequences of a residency requirement. The planner must select regions and configurations that keep data within the permitted jurisdiction.

Question 42Migration Assessment and Planning

When estimating the effort of a rehost migration for a large application, which factor most often dominates the schedule?

  1. The color scheme of the target management console
  2. The time needed to remediate dependencies, networking, and identity integration Correct answer.
  3. The cost of the target virtual machine instance type
  4. The number of characters in the application's source code

Explanation

Rehosting is often described as lift-and-shift, but the real effort lies in adapting dependencies, network paths, identity integration, and operational tooling to the target environment. Instance pricing affects run cost rather than schedule, and code size or interface cosmetics are not schedule drivers. Dependency and integration remediation is the recurring dominant effort.

Question 43Migration Assessment and Planning

An application owner insists their system must be migrated first because it is the most business-critical. How should the planner respond within a dependency-aware wave plan?

  1. Refuse to migrate the system at all until all other systems are complete
  2. Explain that sequencing must respect dependencies and shared services, then place the system as early as those constraints allow Correct answer.
  3. Accept the request and move the system in wave one regardless of its dependencies
  4. Move the system last to minimize risk to the business

Explanation

Wave sequencing is driven by dependencies and shared components; moving a system before its prerequisites exist creates cutover failure. The planner should honor business priority as far as the dependency graph permits rather than ignoring either consideration. Blanket refusal or deferring to last both disregard the stated criticality.

Question 44Migration Assessment and Planning

Which discovery data source is most reliable for identifying actual network connections between servers during a migration assessment?

  1. Flow logs and network traffic analysis collected over a representative period Correct answer.
  2. The original project documentation written at system deployment
  3. The vendor's published architecture reference diagrams
  4. Interviews with application owners about how they believe systems connect

Explanation

Observed traffic over a representative period reflects actual runtime behavior, including undocumented connections. Interviews and old documentation capture intent and may be stale or incomplete. Vendor reference diagrams describe generic product architecture rather than this environment's real traffic.

Question 45Migration Assessment and Planning

A migration plan proposes moving a stateful application's database to a managed cloud service while keeping the application tier rehosted. Which planning consideration is most important?

  1. Verifying that the managed database supports the application's original operating system
  2. Confirming that the application tier can be rewritten in a new language
  3. Ensuring the database runs on the same physical host as the application tier
  4. Ensuring the rehosted tier can reach the managed database securely with acceptable latency Correct answer.

Explanation

A hybrid pattern of rehosted compute with a managed database depends on secure, low-latency connectivity between tiers, typically through private networking and appropriate identity controls. Language rewrites, operating system compatibility for a managed service, and co-location on the same host are not requirements of this pattern. Connectivity and latency are the decisive planning factors.

Question 46Migration Assessment and Planning

Which metric is most useful for sizing the target environment during assessment of a compute-heavy workload?

  1. Peak and sustained CPU, memory, and I/O utilization over a representative period Correct answer.
  2. The count of database tables in the application schema
  3. The number of source code files in the repository
  4. The number of user accounts created in the directory

Explanation

Right-sizing requires observed utilization of CPU, memory, and I/O at both peak and sustained levels so the target can handle demand without overprovisioning. Code file counts, table counts, and directory account totals do not measure resource consumption. Utilization data over a representative window is the standard sizing input.

Question 47Migration Assessment and Planning

During assessment, a team finds several applications sharing a single large database with no clear ownership boundaries. What is the most prudent planning recommendation?

  1. Immediately split the database into per-application schemas before any migration
  2. Move each application to a different cloud provider to isolate them
  3. Migrate the shared database as a single unit and defer decomposition to a later phase Correct answer.
  4. Retire all applications that depend on the shared database

Explanation

Shared databases are common and decomposing them is risky and time-consuming; the prudent plan migrates the shared asset intact to preserve behavior and defers decomposition to a deliberate later phase. Immediate splitting adds risk before the move is even validated, and retirement or multi-provider sprawl are disproportionate responses. Preserving behavior first is the standard sequencing principle.

Question 48Migration Assessment and Planning

Which element belongs in a migration readiness assessment for the workforce rather than for the technology?

  1. Inventorying the installed operating system versions
  2. Mapping the VLAN structure of the data center
  3. Identifying which staff have cloud operations skills and where training gaps exist Correct answer.
  4. Measuring the IOPS of the current storage array

Explanation

Workforce readiness assesses whether the people who will operate and support the future environment have the necessary skills, and where training or hiring is required. IOPS measurement, VLAN mapping, and OS inventory are technical discovery activities. Skills gap analysis is the people-side counterpart to technical readiness.

Question 49Migration Assessment and Planning

A migration assessment identifies an application with no active users but which still incurs license and hosting costs. Which action should the plan recommend first?

  1. Repurchase a newer version from the vendor
  2. Refactor it into a modern architecture for future use
  3. Confirm with business owners that it is truly unused, then retire it Correct answer.
  4. Rehost it to a smaller cloud instance to reduce cost

Explanation

An apparently unused system should be validated with business owners before any investment, and if confirmed unused it should be retired to eliminate cost and risk immediately. Rehosting, refactoring, or repurchasing all spend money to preserve something that may deliver no value. Validation followed by retirement is the correct first step.

Question 50Migration Assessment and Planning

Which risk in a migration assessment is best mitigated by maintaining a tested rollback path for each wave?

  1. Loss of staff certifications
  2. Delays in vendor contract negotiation
  3. Cost overrun on cloud consumption
  4. A failed cutover that leaves users without service Correct answer.

Explanation

A tested rollback path addresses the operational risk that a cutover does not succeed and service must be restored quickly on the source environment. Cost overrun, certification loss, and contract delays are governance and financial risks that rollback does not mitigate. Rollback planning is specifically a cutover-risk control.