Free Citrix 1Y0-312 Actual Exam Questions - Question 14 Discussion

B/C? The ELM Management Console (B) is where you manage layers, so it might have settings to change priority directly through the GUI. On the other hand, PowerShell on the Delivery Controller (C) is powerful for app layer configs, and changing priority could be one of those command-line tweaks it supports. I’m less sure about the LayerPriority Utility (D) being universally available or necessary if these tools can do the job, so maybe it’s safer to pick one of these more standard options.

Option D sounds right to me since it’s literally named for adjusting layer priority, so it seems made for this exact task rather than using broader tools like PowerShell or ELM.

C imo—PowerShell on the Delivery Controller usually handles app layer stuff directly, so it feels more precise for priority tweaks than messing with ELM or separate utilities.

A, since PowerShell on ELM server can script priority changes without extra tools.

Maybe B. The ELM Management console should have built-in options for adjusting application layer priorities without needing extra utilities or scripting. It feels more user-friendly than digging into PowerShell or separate tools.

Probably D here. The LayerPriority Utility is specifically designed for adjusting layer priorities, so it’s the most targeted tool for this job. While the ELM console might let you manage layers broadly, changing priority usually calls for the utility made just for that purpose, especially in setups that support it. If the question’s context doesn’t specify a version where the utility is obsolete, D makes the most sense as a direct solution.

B/D? I’m thinking the ELM Management console (B) might offer a straightforward way to tweak layer priorities without messing with scripts or separate utilities. If it’s designed for managing layers, it should cover priority changes too. On the other hand, the LayerPriority Utility (D) sounds like it’s built specifically for this, so it might be more precise. But yeah, if version compatibility is an issue with D, then B could be more reliable across different setups. Wouldn’t count out B just yet.

Maybe B, since the ELM Management console usually handles layer configurations and could have priority settings built in, making it a user-friendly choice without command lines.

Option C feels right since Delivery Controller handles app delivery settings directly.

C/D? Since the Delivery Controller manages app delivery, using PowerShell on it (C) could adjust priorities broadly, while the LayerPriority Utility (D) is a more specialized but possibly version-limited tool.

D/C? The utility (D) seems purpose-built for layer priority changes, but if it’s not always supported, PowerShell on Delivery Controller (C) might do it through scripting. Not sure if ELM options (A/B) can adjust app layers though.

D imo, it’s specifically made to adjust layer priorities, not just a generic tool.

Maybe C because PowerShell on the Delivery Controller often handles app and delivery settings directly, so it might be used to adjust layer priorities without extra tools.

Not B, the ELM console is mainly for monitoring and reporting, not for changing app layer priorities. The LayerPriority Utility (D) seems designed for this exact purpose.

D imo, LayerPriority Utility sounds spot on for changing app layer priority.