Developing Mobile Apps v1.0 (70-357)

Page:    1 / 4   
Total 51 questions

Case Study -
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background -
You are developing an application named Timeline that presents information on a timeline. The app allows users to create items and enter details about the item.
The app displays item names on a timeline. When users select an item name on the timeline, the app displays additional content about the item.

Business requirements -

Timeline section -
The timeline element of the app has the following layout requirements:
-> The timeline must adapt to the screen size and orientation of the device.
-> The timeline size must dynamically change if the window containing the content is resized by the user.
-> The user must be able to scroll through the timeline horizontally when the device is in landscape mode.
-> The user must be able to scroll through the timeline vertically when the device is in portrait mode.
-> The timeline must begin scrolling as soon as a scroll is detected. Scrolling must continue for a short distance after the scroll input has stopped.
-> Scroll bars or panning controls must always be visible.
The following image depicts the layout for the timeline section of the app when the device is using landscape orientation:


The following image depicts the layout for the timeline section of the app when the device is using portrait orientation:


Content section -
The content element of the app has the following layout requirements:
-> When a user selects an item on the timeline, the details for that item must display beneath or to the right of the timeline.
-> The content section must display one page of information. The element must be a child of the selected item in the timeline.
-> Users must be able to return to a previously selected event by pressing the Back button.

User interface -
The user must be able to navigate the application using the interface below:

-> The Favorite button marks the current content to be displayed in a Favorites panel.
-> The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
-> The Notes button allows the user to manage notes about the current content.
-> The app must support touch, mouse, and stylus input.
-> The app layout must automatically adapt to the screen size and orientation.

Technical requirements -

Layout -
You identify the following layout requirements:

General -
-> All user interface (UI) elements must continuously scale when a user resizes the window.
-> UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
-> UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.

Timeline -
-> The timeline must be displayed in a horizontal layout when the device is in a landscape orientation or when the horizontal width is greater than the vertical height.
-> The timeline must be displayed in a vertical layout when the device is in a portrait orientation or when the vertical height is greater than the horizontal width.
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
-> The app must only allow one level of detail to be linked to each item in the timeline.

Optimization -
You must optimize the app using the following guidelines:
-> You must minimize the time it takes to display content when an item on the timeline is selected.
-> The app must respect memory and resource constraints for all devices.

XAML coding style -
All code and markup must conform to the following style guidelines:
-> Use resource dictionaries for styles that are used more than once.
-> Limit the use of nested panels.
-> Use built-in properties of existing panels instead of using separate style objects.
-> Use the navigation structure that best models the data without exceeding the requirements of the app.

Application structure -

MainPage.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


Settings.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


ResourceDictionery.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only.)


MainPage.xaml.cs -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.
You need to implement the appropriate XAML layout for the Timeline app.
Solution: You create an instance of a StackPanel class.
Does this meet the goal?

  • A. Yes
  • B. No


Answer : B

Explanation:
StackPanel is a simple layout panel that arranges its child elements into a single line that can be oriented horizontally or vertically. StackPanel controls are typically used in scenarios where you want to arrange a small subsection of the UI on your page.
The following XAML shows how to create a vertical StackPanel of items.

XAML -
<StackPanel>
<Rectangle Fill="Red" Height="44"/>
<Rectangle Fill="Blue" Height="44"/>
<Rectangle Fill="Green" Height="44"/>
<Rectangle Fill="Orange" Height="44"/>
</StackPanel>
The result looks like this.


Reference: https://docs.microsoft.com/en-us/windows/uwp/layout/layout-panels

Case Study -
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background -
You are developing an application named Timeline that presents information on a timeline. The app allows users to create items and enter details about the item.
The app displays item names on a timeline. When users select an item name on the timeline, the app displays additional content about the item.

Business requirements -

Timeline section -
-> The timeline element of the app has the following layout requirements:
-> The timeline must adapt to the screen size and orientation of the device.
-> The timeline size must dynamically change if the window containing the content is resized by the user.
-> The user must be able to scroll through the timeline horizontally when the device is in landscape mode.
-> The user must be able to scroll through the timeline vertically when the device is in portrait mode.
-> The timeline must begin scrolling as soon as a scroll is detected. Scrolling must continue for a short distance after the scroll input has stopped.
-> Scroll bars or panning controls must always be visible.
The following image depicts the layout for the timeline section of the app when the device is using landscape orientation:


The following image depicts the layout for the timeline section of the app when the device is using portrait orientation:


Content section -
The content element of the app has the following layout requirements:
When a user selects an item on the timeline, the details for that item must display beneath or to the right of the timeline.

-> The content section must display one page of information. The element must be a child of the selected item in the timeline.
-> Users must be able to return to a previously selected event by pressing the Back button.

User interface -
The user must be able to navigate the application using the interface below:

-> The Favorite button marks the current content to be displayed in a Favorites panel.
-> The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
-> The Notes button allows the user to manage notes about the current content.
-> The app must support touch, mouse, and stylus input.
-> The app layout must automatically adapt to the screen size and orientation.

Technical requirements -

Layout -
You identify the following layout requirements:

General -
-> All user interface (UI) elements must continuously scale when a user resizes the window.
-> UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
-> UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.

Timeline -
-> The timeline must be displayed in a horizontal layout when the device is in a landscape orientation or when the horizontal width is greater than the vertical height.
-> The timeline must be displayed in a vertical layout when the device is in a portrait orientation or when the vertical height is greater than the horizontal width.
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
-> The app must only allow one level of detail to be linked to each item in the timeline.

Optimization -
You must optimize the app using the following guidelines:
You must minimize the time it takes to display content when an item on the timeline is selected.

-> The app must respect memory and resource constraints for all devices.

XAML coding style -
All code and markup must conform to the following style guidelines:
-> Use resource dictionaries for styles that are used more than once.
-> Limit the use of nested panels.
-> Use built-in properties of existing panels instead of using separate style objects.
-> Use the navigation structure that best models the data without exceeding the requirements of the app.

Application structure -

MainPage.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


Settings.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


ResourceDictionery.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only.)


MainPage.xaml.cs -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.
You need to implement the appropriate XAML layout for the Timeline app.
Solution: You create an instance of a RelativePanel class.
Does this meet the goal?

  • A. Yes
  • B. No


Answer : A

Explanation:
RelativePanel lets you layout UI elements by specifying where they go in relation to other elements and in relation to the panel. By default, an element is positioned in the upper left corner of the panel.
Reference: https://docs.microsoft.com/en-us/windows/uwp/layout/layout-panels

Case Study -
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background -
You are developing an application named Timeline that presents information on a timeline. The app allows users to create items and enter details about the item.
The app displays item names on a timeline. When users select an item name on the timeline, the app displays additional content about the item.

Business requirements -

Timeline section -
-> The timeline element of the app has the following layout requirements:
-> The timeline must adapt to the screen size and orientation of the device.
-> The timeline size must dynamically change if the window containing the content is resized by the user.
-> The user must be able to scroll through the timeline horizontally when the device is in landscape mode.
-> The user must be able to scroll through the timeline vertically when the device is in portrait mode.
-> The timeline must begin scrolling as soon as a scroll is detected. Scrolling must continue for a short distance after the scroll input has stopped.
-> Scroll bars or panning controls must always be visible.
The following image depicts the layout for the timeline section of the app when the device is using landscape orientation:


The following image depicts the layout for the timeline section of the app when the device is using portrait orientation:


Content section -
The content element of the app has the following layout requirements:
-> When a user selects an item on the timeline, the details for that item must display beneath or to the right of the timeline.
-> The content section must display one page of information. The element must be a child of the selected item in the timeline.
-> Users must be able to return to a previously selected event by pressing the Back button.

User interface -
The user must be able to navigate the application using the interface below:

-> The Favorite button marks the current content to be displayed in a Favorites panel.
-> The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
-> The Notes button allows the user to manage notes about the current content.
-> The app must support touch, mouse, and stylus input.
-> The app layout must automatically adapt to the screen size and orientation.

Technical requirements -

Layout -
You identify the following layout requirements:

General -
-> All user interface (UI) elements must continuously scale when a user resizes the window.
-> UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
-> UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.

Timeline -
-> The timeline must be displayed in a horizontal layout when the device is in a landscape orientation or when the horizontal width is greater than the vertical height.
-> The timeline must be displayed in a vertical layout when the device is in a portrait orientation or when the vertical height is greater than the horizontal width.
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
-> The app must only allow one level of detail to be linked to each item in the timeline.

Optimization -
You must optimize the app using the following guidelines:
-> You must minimize the time it takes to display content when an item on the timeline is selected.
-> The app must respect memory and resource constraints for all devices.

XAML coding style -
All code and markup must conform to the following style guidelines:
-> Use resource dictionaries for styles that are used more than once.
-> Limit the use of nested panels.
-> Use built-in properties of existing panels instead of using separate style objects.
-> Use the navigation structure that best models the data without exceeding the requirements of the app.

Application structure -

MainPage.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


Settings.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


ResourceDictionery.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only.)


MainPage.xaml.cs -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.
You need to implement the appropriate XAML layout for the Timeline app.
Solution: You create an instance of a SplitView control.
Does this meet the goal?

  • A. Yes
  • B. No


Answer : B

Explanation:
A split view control has an expandable/collapsible pane and a content area.
Here is an example of the Microsoft Edge app using SplitView to show its Hub.


Reference: https://docs.microsoft.com/en-us/windows/uwp/controls-and-patterns/split-view

DRAG DROP -

Case Study -
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background -
You are developing an application named Timeline that presents information on a timeline. The app allows users to create items and enter details about the item.
The app displays item names on a timeline. When users select an item name on the timeline, the app displays additional content about the item.

Business requirements -

Timeline section -
-> The timeline element of the app has the following layout requirements:
-> The timeline must adapt to the screen size and orientation of the device.
-> The timeline size must dynamically change if the window containing the content is resized by the user.
-> The user must be able to scroll through the timeline horizontally when the device is in landscape mode.
-> The user must be able to scroll through the timeline vertically when the device is in portrait mode.
-> The timeline must begin scrolling as soon as a scroll is detected. Scrolling must continue for a short distance after the scroll input has stopped.
-> Scroll bars or panning controls must always be visible.
The following image depicts the layout for the timeline section of the app when the device is using landscape orientation:


The following image depicts the layout for the timeline section of the app when the device is using portrait orientation:


Content section -
The content element of the app has the following layout requirements:
-> When a user selects an item on the timeline, the details for that item must display beneath or to the right of the timeline.
-> The content section must display one page of information. The element must be a child of the selected item in the timeline.
-> Users must be able to return to a previously selected event by pressing the Back button.

User interface -
The user must be able to navigate the application using the interface below:

-> The Favorite button marks the current content to be displayed in a Favorites panel.
-> The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
-> The Notes button allows the user to manage notes about the current content.
-> The app must support touch, mouse, and stylus input.
-> The app layout must automatically adapt to the screen size and orientation.

Technical requirements -

Layout -
You identify the following layout requirements:

General -
-> All user interface (UI) elements must continuously scale when a user resizes the window.
-> UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
-> UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.

Timeline -
-> The timeline must be displayed in a horizontal layout when the device is in a landscape orientation or when the horizontal width is greater than the vertical height.
-> The timeline must be displayed in a vertical layout when the device is in a portrait orientation or when the vertical height is greater than the horizontal width.
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
-> The app must only allow one level of detail to be linked to each item in the timeline.

Optimization -
You must optimize the app using the following guidelines:
-> You must minimize the time it takes to display content when an item on the timeline is selected.
-> The app must respect memory and resource constraints for all devices.

XAML coding style -
All code and markup must conform to the following style guidelines:
-> Use resource dictionaries for styles that are used more than once.
-> Limit the use of nested panels.
-> Use built-in properties of existing panels instead of using separate style objects.
-> Use the navigation structure that best models the data without exceeding the requirements of the app.

Application structure -

MainPage.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


Settings.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


ResourceDictionery.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only.)


MainPage.xaml.cs -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to create the user interface for the timeline.
Which four markup segments should you use to develop the solution? To answer, move the appropriate markup segments from the list of markup segments to the answer area and arrange them in the correct order.
NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.
Select and Place:



Answer :

Explanation:
Box 1: <Commandbar>
Command bars (also called "app bars") provide users with easy access to your app's most common tasks, and can be used to show commands or options that are specific to the user's context, such as a photo selection or drawing mode. They can also be used for navigation among app pages or between app sections.
Command bars can be used with any navigation pattern.
XAML provides both the AppBar control and the CommandBar control. You should use the AppBar only when you are upgrading a Universal Windows 8 app that uses the AppBar, and need to minimize changes. For new apps in Windows 10, we recommend using the CommandBar control instead.
Box 2: <AppBarButton .. etc.
The CommandBar control is a general-purpose, flexible, light-weight control that can display both complex content, such as images or text blocks, as well as simple commands such as AppBarButton, AppBarToggleButton, and AppBarSeparator controls.
Box 3: <CommandBar.SecondaryCommands> etc.
The overflow menu is shown only when the command bar is open and the SecondaryCommands property is populated. The new dynamic overflow behavior will automatically move primary commands into the SecondaryCommands area when space is limited.
Box 4: </Commandbar>
Example: Here is a same command bar in its open state. The labels identify the main parts of the control.


This example creates the command bar shown above.
<CommandBar>
<AppBarToggleButton Icon="Shuffle" Label="Shuffle" Click="AppBarButton_Click" />
<AppBarToggleButton Icon="RepeatAll" Label="Repeat" Click="AppBarButton_Click"/>
<AppBarSeparator/>
<AppBarButton Icon="Back" Label="Back" Click="AppBarButton_Click"/>
<AppBarButton Icon="Stop" Label="Stop" Click="AppBarButton_Click"/>
<AppBarButton Icon="Play" Label="Play" Click="AppBarButton_Click"/>
<AppBarButton Icon="Forward" Label="Forward" Click="AppBarButton_Click"/>
<CommandBar.SecondaryCommands>
<AppBarButton Icon="Like" Label="Like" Click="AppBarButton_Click"/>
<AppBarButton Icon="Dislike" Label="Dislike" Click="AppBarButton_Click"/>
</CommandBar.SecondaryCommands>
<CommandBar.Content>
<TextBlock Text="Now playing..." Margin="12,14"/>
</CommandBar.Content>
</CommandBar>
Reference: https://docs.microsoft.com/en-us/windows/uwp/controls-and-patterns/app-bars

Case Study -
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background -
You are developing an application named Timeline that presents information on a timeline. The app allows users to create items and enter details about the item.
The app displays item names on a timeline. When users select an item name on the timeline, the app displays additional content about the item.

Business requirements -

Timeline section -
The timeline element of the app has the following layout requirements:
-> The timeline must adapt to the screen size and orientation of the device.
-> The timeline size must dynamically change if the window containing the content is resized by the user.
-> The user must be able to scroll through the timeline horizontally when the device is in landscape mode.
-> The user must be able to scroll through the timeline vertically when the device is in portrait mode.
-> The timeline must begin scrolling as soon as a scroll is detected. Scrolling must continue for a short distance after the scroll input has stopped.
-> Scroll bars or panning controls must always be visible.
The following image depicts the layout for the timeline section of the app when the device is using landscape orientation:


The following image depicts the layout for the timeline section of the app when the device is using portrait orientation:


Content section -
The content element of the app has the following layout requirements:
-> When a user selects an item on the timeline, the details for that item must display beneath or to the right of the timeline.
-> The content section must display one page of information. The element must be a child of the selected item in the timeline.
-> Users must be able to return to a previously selected event by pressing the Back button.

User interface -
The user must be able to navigate the application using the interface below:

-> The Favorite button marks the current content to be displayed in a Favorites panel.
-> The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
-> The Notes button allows the user to manage notes about the current content.
-> The app must support touch, mouse, and stylus input.
-> The app layout must automatically adapt to the screen size and orientation.

Technical requirements -

Layout -
You identify the following layout requirements:

General -
-> All user interface (UI) elements must continuously scale when a user resizes the window.
-> UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
-> UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.

Timeline -
-> The timeline must be displayed in a horizontal layout when the device is in a landscape orientation or when the horizontal width is greater than the vertical height.
-> The timeline must be displayed in a vertical layout when the device is in a portrait orientation or when the vertical height is greater than the horizontal width.
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
-> The app must only allow one level of detail to be linked to each item in the timeline.

Optimization -
You must optimize the app using the following guidelines:
-> You must minimize the time it takes to display content when an item on the timeline is selected.
-> The app must respect memory and resource constraints for all devices.

XAML coding style -
All code and markup must conform to the following style guidelines:
-> Use resource dictionaries for styles that are used more than once.
-> Limit the use of nested panels.
-> Use built-in properties of existing panels instead of using separate style objects.
-> Use the navigation structure that best models the data without exceeding the requirements of the app.

Application structure -

MainPage.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


Settings.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


ResourceDictionery.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only.)


MainPage.xaml.cs -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to design the navigation for the timeline.
What navigation should you use?

  • A. hierarchy
  • B. peer
  • C. hub
  • D. master/details


Answer : A

Explanation:
From scenario:
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
The app must only allow one level of detail to be linked to each item in the timeline.


Here we can use a hierarchy with each parent node having only one single child node.
Hierarchical structures are good for organizing complex content that spans lots of pages or when pages should be viewed in a particular order. The downside is that hierarchical pages introduce some navigation overhead: the deeper the structure, the more clicks it takes for users to get from page to page.
We recommend a hiearchical structure when:
You expect the user to traverse the pages in a specific order. Arrange the hierarchy to enforce that order.
There is a clear parent-child relationship between one of the pages and the other pages in the group.
There are more than 7 pages in the group.
When there are more than 7 pages in the group, it might be difficult for users to understand how the pages are unique or to understand their current location within the group. If you don't think that's an issue for your app, go ahead and make the pages peers
Reference: https://docs.microsoft.com/en-us/windows/uwp/layout/navigation-basics

Case Study -
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background -
You are developing an application named Timeline that presents information on a timeline. The app allows users to create items and enter details about the item.
The app displays item names on a timeline. When users select an item name on the timeline, the app displays additional content about the item.

Business requirements -

Timeline section -
The timeline element of the app has the following layout requirements:
-> The timeline must adapt to the screen size and orientation of the device.
-> The timeline size must dynamically change if the window containing the content is resized by the user.
The user must be able to scroll through the timeline horizontally when the device is in landscape mode.


-> The user must be able to scroll through the timeline vertically when the device is in portrait mode.
-> The timeline must begin scrolling as soon as a scroll is detected. Scrolling must continue for a short distance after the scroll input has stopped.
-> Scroll bars or panning controls must always be visible.
The following image depicts the layout for the timeline section of the app when the device is using landscape orientation:

The following image depicts the layout for the timeline section of the app when the device is using portrait orientation:


Content section -
The content element of the app has the following layout requirements:
-> When a user selects an item on the timeline, the details for that item must display beneath or to the right of the timeline.
-> The content section must display one page of information. The element must be a child of the selected item in the timeline.
-> Users must be able to return to a previously selected event by pressing the Back button.

User interface -
The user must be able to navigate the application using the interface below:

-> The Favorite button marks the current content to be displayed in a Favorites panel.
-> The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
-> The Notes button allows the user to manage notes about the current content.
-> The app must support touch, mouse, and stylus input.
-> The app layout must automatically adapt to the screen size and orientation.

Technical requirements -

Layout -
You identify the following layout requirements:

General -
-> All user interface (UI) elements must continuously scale when a user resizes the window.
-> UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
-> UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.

Timeline -
-> The timeline must be displayed in a horizontal layout when the device is in a landscape orientation or when the horizontal width is greater than the vertical height.
-> The timeline must be displayed in a vertical layout when the device is in a portrait orientation or when the vertical height is greater than the horizontal width.
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
-> The app must only allow one level of detail to be linked to each item in the timeline.

Optimization -
You must optimize the app using the following guidelines:
-> You must minimize the time it takes to display content when an item on the timeline is selected.
-> The app must respect memory and resource constraints for all devices.

XAML coding style -
All code and markup must conform to the following style guidelines:
-> Use resource dictionaries for styles that are used more than once.
-> Limit the use of nested panels.
-> Use built-in properties of existing panels instead of using separate style objects.
-> Use the navigation structure that best models the data without exceeding the requirements of the app.

Application structure -

MainPage.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


Settings.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


ResourceDictionery.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only.)


MainPage.xaml.cs -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to ensure that the Timeline app meets the XAML coding requirements.
In Settings,xaml, which markup segment should you select to replace the markup segment at line AS06?
A.

B.

C.

D.

  • A. Option A
  • B. Option B
  • C. Option C
  • D. Option D


Answer : A

Explanation:
From scenario: All code and markup must conform to the following style guidelines:
-> Use resource dictionaries for styles that are used more than once.
-> Use built-in properties of existing panels instead of using separate style objects.
XAML resources are objects that are referenced from markup more than once. Resources are defined in a ResourceDictionary, typically in a separate file or at the top of the markup page. In this scenario the ResourceDictionary is defined in the ResourceDictionery.xaml file.
You access members of the resource dictionary like any other dictionary.
Reference: https://docs.microsoft.com/en-us/windows/uwp/controls-and-patterns/resourcedictionary-and-xaml-resource-references

HOTSPOT -

Case Study -
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background -
You are developing an application named Timeline that presents information on a timeline. The app allows users to create items and enter details about the item.
The app displays item names on a timeline. When users select an item name on the timeline, the app displays additional content about the item.

Business requirements -

Timeline section -
The timeline element of the app has the following layout requirements:
-> The timeline must adapt to the screen size and orientation of the device.
-> The timeline size must dynamically change if the window containing the content is resized by the user.
-> The user must be able to scroll through the timeline horizontally when the device is in landscape mode.
-> The user must be able to scroll through the timeline vertically when the device is in portrait mode.
-> The timeline must begin scrolling as soon as a scroll is detected. Scrolling must continue for a short distance after the scroll input has stopped.
-> Scroll bars or panning controls must always be visible.
The following image depicts the layout for the timeline section of the app when the device is using landscape orientation:


The following image depicts the layout for the timeline section of the app when the device is using portrait orientation:


Content section -
The content element of the app has the following layout requirements:
-> When a user selects an item on the timeline, the details for that item must display beneath or to the right of the timeline.
-> The content section must display one page of information. The element must be a child of the selected item in the timeline.
-> Users must be able to return to a previously selected event by pressing the Back button.

User interface -
The user must be able to navigate the application using the interface below:

-> The Favorite button marks the current content to be displayed in a Favorites panel.
-> The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
-> The Notes button allows the user to manage notes about the current content.
-> The app must support touch, mouse, and stylus input.
-> The app layout must automatically adapt to the screen size and orientation.

Technical requirements -

Layout -
You identify the following layout requirements:

General -
All user interface (UI) elements must continuously scale when a user resizes the window.

-> UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
-> UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.

Timeline -
-> The timeline must be displayed in a horizontal layout when the device is in a landscape orientation or when the horizontal width is greater than the vertical height.
-> The timeline must be displayed in a vertical layout when the device is in a portrait orientation or when the vertical height is greater than the horizontal width.
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
-> The app must only allow one level of detail to be linked to each item in the timeline.

Optimization -
You must optimize the app using the following guidelines:
-> You must minimize the time it takes to display content when an item on the timeline is selected.
-> The app must respect memory and resource constraints for all devices.

XAML coding style -
All code and markup must conform to the following style guidelines:
-> Use resource dictionaries for styles that are used more than once.
-> Limit the use of nested panels.
-> Use built-in properties of existing panels instead of using separate style objects.
-> Use the navigation structure that best models the data without exceeding the requirements of the app.

Application structure -

MainPage.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


Settings.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


ResourceDictionery.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only.)


MainPage.xaml.cs -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to properly handle the size of the user interface objects.
How should you complete the method? To answer, select the appropriate code segment from each list in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:



Answer :

Explanation:
From scenario:
UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.
Box 1: MouseCapabilities pd = new Windows.Devices.Input.MouseCapabilities();
The Windows.Devices.Input namespace contains the MouseCapabilities class used to retrieve the properties exposed by one or more connected mice. Just create a new MouseCapabilities object and get the properties you're interested in.
Box 2: int pointer = pd.MousePresent;
Example:
MouseCapabilities mouseCapabilities = new Windows.Devices.Input.MouseCapabilities();
MousePresent.Text = mouseCapabilities.MousePresent != 0 ? "Yes" : "No";
Box 3: if (pointer == 1)
This is true if a mouse is present.
Reference: https://docs.microsoft.com/en-us/windows/uwp/input-and-devices/identify-input-devices

HOTSPOT -

Case Study -
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background -
You are developing an application named Timeline that presents information on a timeline. The app allows users to create items and enter details about the item.
The app displays item names on a timeline. When users select an item name on the timeline, the app displays additional content about the item.

Business requirements -

Timeline section -
The timeline element of the app has the following layout requirements:
-> The timeline must adapt to the screen size and orientation of the device.
-> The timeline size must dynamically change if the window containing the content is resized by the user.
-> The user must be able to scroll through the timeline horizontally when the device is in landscape mode.
-> The user must be able to scroll through the timeline vertically when the device is in portrait mode.
-> The timeline must begin scrolling as soon as a scroll is detected. Scrolling must continue for a short distance after the scroll input has stopped.
-> Scroll bars or panning controls must always be visible.
The following image depicts the layout for the timeline section of the app when the device is using landscape orientation:


The following image depicts the layout for the timeline section of the app when the device is using portrait orientation:


Content section -
The content element of the app has the following layout requirements:
-> When a user selects an item on the timeline, the details for that item must display beneath or to the right of the timeline.
-> The content section must display one page of information. The element must be a child of the selected item in the timeline.
-> Users must be able to return to a previously selected event by pressing the Back button.

User interface -
The user must be able to navigate the application using the interface below:

-> The Favorite button marks the current content to be displayed in a Favorites panel.
-> The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
-> The Notes button allows the user to manage notes about the current content.
-> The app must support touch, mouse, and stylus input.
-> The app layout must automatically adapt to the screen size and orientation.

Technical requirements -

Layout -
You identify the following layout requirements:

General -
All user interface (UI) elements must continuously scale when a user resizes the window.
-> UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
-> UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.

Timeline -
-> The timeline must be displayed in a horizontal layout when the device is in a landscape orientation or when the horizontal width is greater than the vertical height.
-> The timeline must be displayed in a vertical layout when the device is in a portrait orientation or when the vertical height is greater than the horizontal width.
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
-> The app must only allow one level of detail to be linked to each item in the timeline.

Optimization -
You must optimize the app using the following guidelines:
-> You must minimize the time it takes to display content when an item on the timeline is selected.
-> The app must respect memory and resource constraints for all devices.

XAML coding style -
All code and markup must conform to the following style guidelines:
Use resource dictionaries for styles that are used more than once.

-> Limit the use of nested panels.
-> Use built-in properties of existing panels instead of using separate style objects.
-> Use the navigation structure that best models the data without exceeding the requirements of the app.

Application structure -

MainPage.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


Settings.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


ResourceDictionery.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only.)


MainPage.xaml.cs -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)

You are reviewing the App_BackRequested method in the MainPage.xaml.cs file.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:



Answer :

Explanation:

Box 1: No -
If we assume that the client is a PC, then the back button is not available in tablet mode.

Box 2: Yes -
If we assume that the client is a PC, then the back button is available in desktop mode.

Box 3: No -
The user cannot go back from the first item on the timeline.

Box 4: No -
From scenario: The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
Reference: https://docs.microsoft.com/en-us/windows/uwp/layout/navigation-history-and-backwards-navigation

Case Study -
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background -
You are developing an application named Timeline that presents information on a timeline. The app allows users to create items and enter details about the item.
The app displays item names on a timeline. When users select an item name on the timeline, the app displays additional content about the item.

Business requirements -

Timeline section -
The timeline element of the app has the following layout requirements:
-> The timeline must adapt to the screen size and orientation of the device.
-> The timeline size must dynamically change if the window containing the content is resized by the user.
-> The user must be able to scroll through the timeline horizontally when the device is in landscape mode.
-> The user must be able to scroll through the timeline vertically when the device is in portrait mode.
-> The timeline must begin scrolling as soon as a scroll is detected. Scrolling must continue for a short distance after the scroll input has stopped.
-> Scroll bars or panning controls must always be visible.
The following image depicts the layout for the timeline section of the app when the device is using landscape orientation:


The following image depicts the layout for the timeline section of the app when the device is using portrait orientation:


Content section -
The content element of the app has the following layout requirements:
-> When a user selects an item on the timeline, the details for that item must display beneath or to the right of the timeline.
-> The content section must display one page of information. The element must be a child of the selected item in the timeline.
-> Users must be able to return to a previously selected event by pressing the Back button.

User interface -
The user must be able to navigate the application using the interface below:

-> The Favorite button marks the current content to be displayed in a Favorites panel.
-> The Back and Forward buttons navigate through the app selection history. Both buttons must be available on all devices.
-> The Notes button allows the user to manage notes about the current content.
-> The app must support touch, mouse, and stylus input.
-> The app layout must automatically adapt to the screen size and orientation.

Technical requirements -

Layout -
You identify the following layout requirements:

General -
All user interface (UI) elements must continuously scale when a user resizes the window.

-> UI controls must be smaller and spaced closer together if there is a mouse or stylus available.
-> UI controls must be larger and spaced farther apart if the device supports touch and there is no mouse or pointer available.

Timeline -
-> The timeline must be displayed in a horizontal layout when the device is in a landscape orientation or when the horizontal width is greater than the vertical height.
-> The timeline must be displayed in a vertical layout when the device is in a portrait orientation or when the vertical height is greater than the horizontal width.
-> Each item in the past must be linked to the next item in the future.
-> Users must be able to scroll from past events to future events or from future events to past events.
-> The app must only allow one level of detail to be linked to each item in the timeline.

Optimization -
You must optimize the app using the following guidelines:
-> You must minimize the time it takes to display content when an item on the timeline is selected.
-> The app must respect memory and resource constraints for all devices.

XAML coding style -
All code and markup must conform to the following style guidelines:
-> Use resource dictionaries for styles that are used more than once.
-> Limit the use of nested panels.
-> Use built-in properties of existing panels instead of using separate style objects.
-> Use the navigation structure that best models the data without exceeding the requirements of the app.

Application structure -

MainPage.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


Settings.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)


ResourceDictionery.xaml -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only.)


MainPage.xaml.cs -
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to configure the app to meet the load time requirements.
What should you do?

  • A. Set the value of the CacheSize to 0.
  • B. Set the value of the CacheMode property to BitmapCache.
  • C. Set the value of the NavigationCacheMode property to Enabled.
  • D. Set the value of the NavigationCacheMode property to Disabled.


Answer : C

Explanation:
Scenario: You must optimize the app using the following guidelines:
-> You must minimize the time it takes to display content when an item on the timeline is selected.
The app must respect memory and resource constraints for all devices.


You use the NavigationCacheMode property to specify whether a new instance of the page is created for each visit to the page or if a previously constructed instance of the page that has been saved in the cache is used for each visit.
The default value for the NavigationCacheMode property is Disabled. Set the NavigationCacheMode property to Enabled or Required when a new instance of the page is not essential for each visit. By using a cached instance of the page, you can improve the performance of your application and reduce the load on your server.
Reference: https://msdn.microsoft.com/en-us/library/system.windows.controls.page.navigationcachemode(v=vs.95).aspx

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.
You are developing a Universal Windows Platform (UWP) app.
Your app stores files on a user’s device.
You need to be able to replace the existing files with new files generated by the user.
Solution: You run the StorageFile.OpenSequentialReadAsync method to replace the existing file.
Does this meet the goal?

  • A. Yes
  • B. No B


Answer : Explanation

Explanation:
The OpenSequentialReadAsync() method opens a sequential-access stream over the current file for reading file contents.
Reference: https://docs.microsoft.com/en-us/uwp/api/windows.storage.storagefile

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.
You are developing a Universal Windows Platform (UWP) app.
Your app stores files on a user’s device.
You need to be able to replace the existing files with new files generated by the user.
Solution: You run the StorageFile.GetParentAsync method to get a reference to the existing file. Then, you run the StorageFile.CreateStreamedFileAsync method to create the new file at the same location.
Does this meet the goal?

  • A. Yes
  • B. No


Answer : A

Explanation:
The GetParentAsync() method gets the parent folder of the current file.
The CreateStreamedFileAsync method can be used to create a StorageFile that can be passed to other methods or passed to another app through app contracts.
Reference: https://docs.microsoft.com/en-us/uwp/api/windows.storage.storagefile

HOTSPOT -
You have an app that includes the following method:


For each of the following statements, select Yes if the statement is true. Otherwise, select No.
Hot Area:



Answer :

Explanation:

Box 1: No -
When neither DesiredAccuracyInMeters nor DesiredAccuracy are set, your app will use an accuracy setting of 500 meters (which corresponds to the
DesiredAccuracy setting of Default). Setting DesiredAccuracy to Default or High indirectly sets DesiredAccuracyInMeters to 500 or 10 meters, respectively.

Box 2: No -
The Default value should be used to optimize for power, performance, and other cost considerations.
The High value should be used to deliver the most accurate report possible. This includes using services that might charge money, or consuming higher levels of battery power or connection bandwidth. An accuracy level of High may degrade system performance and should be used only when necessary.
Reference:
https://docs.microsoft.com/en-us/uwp/api/windows.devices.geolocation.geolocator https://docs.microsoft.com/en-us/uwp/api/windows.devices.geolocation.positionaccuracy

DRAG DROP -
You are creating a Universal Windows Platform (UWP) app that takes pictures.
You want to use the camera’s built-in interface for taking the pictures.
You need to capture an image from the device’s built-in camera.
How should you complete the method? To answer, drag the appropriate code segments to the correct location or locations. Each code segments 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.
Select and Place:




Answer :

Explanation:

Box 1: CameraCaptureUI -

Box 2: CameraCaptureUI -
Example: Using Windows.Media.Capture.CameraCaptureUI API to capture a photo
CameraCaptureUI dialog = new CameraCaptureUI();
Size aspectRatio = new Size(16, 9);
dialog.PhotoSettings.CroppedAspectRatio = aspectRatio;
StorageFile file = await dialog.CaptureFileAsync(CameraCaptureUIMode.Photo);
Reference: https://docs.microsoft.com/en-us/uwp/api/windows.media.capture.cameracaptureui

HOTSPOT -
You are developing an app that displays photos.
You need to create a method that displays informational text when a user hovers the pointer over a photo.
How should you complete the method? To answer, select the appropriate code segment from each list in the answer area.
Hot Area:




Answer :

Explanation:

Box 1: DependencyObject -

Box 2: String -

Box 3: ToolTip -

Box 4: ToolTip -

Box 5: ToolTipService -
A ToolTip must be assigned to another UI element that is its owner. In Extensible Application Markup Language (XAML), use the ToolTipService.Tooltip attached property to assign the ToolTip to an owner. In code, use the ToolTipService.SetToolTip method to assign the ToolTip to an owner.
The SetToolTip(DependencyObject, Object) method sets the value of the ToolTipService.ToolTip XAML attached property.
Reference: https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.controls.tooltipservice#Windows_UI_Xaml_Controls_ToolTipService_ToolTipProperty

You are developing a Universal Windows Platform (UWP) app.
You need to provide a solution that moves the scroll bars of the ScrollViewer when a user rotates the mouse wheel.
Which two actions should you perform? Each correct answer presents part of the solution.

  • A. Evaluate the CurrentPoint.Properties.MouseWheelDelta property of the PointerEvenArgs object. Call the ChangeView() method of the ScrollViewer.
  • B. Update the XAML of the ScrollViewer to include the PointerWheelChanged event with a new event handler. Evaluate the Pointer.IsInRange property of the PointerRoutedEventArgs object within the event handler. Call the ChangeView() method of the ScrollViewer.
  • C. Add an event handler to the PointerRoutedAway event for the current window.
  • D. Evaluate the CurrentPoint.Properties.IsHorizontalMouseWheel property of the PointerEventArgs object. Call the ChangeView() method of the ScrollViewer.
  • E. Add an event handler to the PointerWheelChanged event for the current window.


Answer : CD

Explanation:
The PointerRoutedAway event occurs on the process receiving input when the pointer input is routed to another process.
Reference:
https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.controls.scrollviewer https://docs.microsoft.com/en-us/uwp/api/windows.ui.core.corewindow#Windows_UI_Core_CoreWindow_PointerWheelChanged

Page:    1 / 4   
Total 51 questions