You must right-size new pooled Windows 11 Enterprise multi-session host pools by assessing current on-premises RDS servers. You want realistic density and performance assumptions. Which two Azure Migrate assessment steps or settings should you use? (Select two answers.)

To accurately right-size, deploy an Azure Migrate appliance and collect performance data for at least 30 days. This duration captures typical usage patterns, including peak loads and monthly cycles, providing realistic data for assessment. Using performance-based sizing with the 95th percentile ensures the assessment considers peak demands, not just averages, preventing under-provisioning. Applying a comfort factor (e.g., 1.3) adds headroom for unexpected spikes or future growth. "As-on-premises sizing" simply replicates current configurations, which may be over or under-provisioned, not optimizing for Azure. Ignoring disk and network metrics is incorrect; while FSLogix offloads profile I/O, session hosts still have OS and application disk I/O, and network traffic is crucial. Assuming 100% user concurrency is unrealistic and leads to significant over-provisioning, incurring unnecessary costs.