It is impossible to pass Microsoft 70-488 exam without any help in the short term. Come to Pass4sure soon and find the most advanced, correct and guaranteed Microsoft 70-488 practice questions. You will get a surprising result by our Abreast of the times Developing Microsoft SharePoint Server 2013 Core Solutions practice guides.
Q71. DRAG DROP - (Topic 5)
You create SharePoint apps for multiple clients.
Each client has a unique environment with specific requirements.
You need to choose the appropriate hosting location for each app.
What should you do? (To answer, drag the appropriate hosting options to the correct
description in the answer area. Each hosting option 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.)
Answer:
Q72. DRAG DROP - (Topic 5)
You administer the SharePoint environment for a company. You create a SharePoint application to manage budgets and expenses. The application requires access to all site collections and resources.
You need to package and publish the budget and expenses app.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Answer:
Q73. - (Topic 1)
You need to ensure that the CourierMobile app determines whether the franchisee owns the account.
What should you do?
A. Use OAuth and App only security. Request the Read right from the http://sharepoint/content/ sitecollection/web/list scope URI.
B. Use OAuth and App+User security. Request the Read right from the http://sharepoint/content/ sitecollection scope URI.
C. Use SPSecurity.RunWithElevatedPrivileges to connect to SharePoint and read from the Accounts list in the site collection.
D. Use the SharePoint user credentials of the bicycle messenger to connect to SharePoint and read from the Accounts list in the site collection.
Answer: B
Explanation: * SharePoint users three types of authorization policies. The user-only policy requires only that the call to SharePoint include an authenticated user identity. The app-only policy requires only that the call include only an authenticated app identity. The user+app policy requires that the call include both kinds of authenticated identities.
* You may have already heard that OAuth 2.0 plays an important role in the authentication and authorization of apps for SharePoint. It does, but it is not necessarily a part of the authorization story for every app for SharePoint. If you plan to build an app for SharePoint that runs in an remote web application and communicates back to SharePoint using server-side code, you will need to use OAuth.
Scenario:
* The CourierMobile app must be able to connect to the SharePoint Customers list and verify whether the account belongs to the franchisee to avoid pickups or deliveries to customers that do not belongs to the franchisee. When the CourierMobile add accesses the Customers list, it must only read its contents with the minimum permissions necessary.
* Margie's Travel provides an API to enable external developers to authenticate by using OAuth and claims-based authentication. Many couriers are members of Margie's Travel
Reference: Authorization and authentication of apps for SharePoint 2013
Q74. - (Topic 5)
You create a cloud-hosted SharePoint app.
You must make the app available in the SharePoint Store for customers to install on their host webs.
You need to keep the style and navigation of the app the same as the host web of the app after it is installed by any customer.
What should you do?
A. Use an app template and an app.master master file for branding.
B. Add a reference to SP.UI.Controls.js on the host web. Pass the AppUrl parameter to the host web. Apply branding to the host web.
C. Copy the CSS file from the app to the host web. Run the Chrome control to convert the CSS file to the host web format. Apply the styles contained in the CSS file to the host web.
D. Add a reference to the SP.UI.Controls.js file located in the new /_layouts/15 directory. Pass the HostUrl parameter to the start page of the app. Use the Chrome control in the HTML page in a declarative manner.
Answer: D
Explanation: Microsoft allows developers to import a very basic version of the SharePoint 2013 chrome into their apps without having to manually create matching HTML controls. The functionality for this can be found in the SP.UI.Controls.js file located in the new /_layouts/15 directory. To use the chrome control, first add a reference to SP.UI.Controls.js (make sure you've already loaded the requisite JQuery files and other dependencies), then add an empty <div> to your page markup at or near the top of the page.
Reference: Using the Chrome Control in SharePoint 2013 Apps
Q75. DRAG DROP - (Topic 5)
You troubleshoot the sandbox solutions that your team builds.
You need to redeploy a sandbox solution. You also need to identify which process must be debugged.
Where should you redeploy the solution, and which process should you debug? (To answer, drag the appropriate statements to the correct location or locations in the answer area. Each statement 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.)
Answer:
Q76. - (Topic 1)
You need to create a custom sign-in page to allow the users of the FranchiseMonitor app to authenticate against SharePoint and Margie's Travel API.
What should you do?
A. Create an app for SharePoint. Set the trust level to Sandbox solution. Create an application page that writes a cookie named FedAuth. Deploy the app and configure the Sign In Page URL in Central Administration Authentication Provider for the zone.
B. Create an app for SharePoint. Set the trust level to Farm solution. Create an application page that writes a cookie named FedAuth. Deploy the app and configure the Sign In Page URL in Central Administration Authentication Provider for the zone.
C. Create an app for SharePoint. Set the trust level to Farm solution. Create an application page that writes a cookie named ASPXAUTH. Deploy the app and configure the Sign In Page URL in Central Administration Authentication Provider for the zone.
D. Create an app for SharePoint. Set the trust level to Sandbox solution. Create an application page that writes a cookie named ASPXAUTH. Deploy the app and configure the Sign In Page URL in Central Administration Authentication Provider for the zone.
Answer: B
Explanation:
The new claims-based authentication in SharePoint 2010 does not use the ASPXAUTH
cookie, instead it uses the FedAuth cookie.
SharePoint 2013 tracks FedAuth cookies in the new distributed cache service using
Windows Server AppFabric Caching.
Scenario: The FranchiseMonitor app must use claims-based authentication, once
launched, to authenticate the franchisee against an API provided by Margie's Travel.
Q77. DRAG DROP - (Topic 4)
You need to create a collaboration template.
Which code segment should you include in Target 1, Target 2, Target 3, Target 4 and Target 5 to complete the code? (To answer, drag the appropriate code segments to the correct targets in the answer area. Each code segment 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.)
Answer:
Q78. - (Topic 3)
After deploying a solution, a code-based hotfix becomes available. You need to deploy the hotfix.
What should you do? (Each correct answer presents part of the solution. Choose all that apply.)
A. Use assembly binding redirection in the web application configuration file.
B. Increment the assembly file version of the assembly.
C. Increment the product version of the assembly.
D. Increment the assembly version of the assembly.
E. Use assembly binding redirection in the assembly policy file.
Answer: A,C
Explanation: A:Assembly versions are everywhere in SharePoint – web.config files, web
part definitions, workflow definitions, event receiver bindings – the list goes on. In each
case, the version number is absolutely required so that SharePoint can load the code to
run at that time. If you update an assembly’s version, you have two choices to ensure your
code can still be loaded:
/ Find and update every reference to the previous assembly version.
/ Use a binding redirect in the relevant .config file (e.g. web.config) to point to the new
version of the assembly.
C: Assembly Version : This is the version number used by framework during build and at runtime to locate, link and load the assemblies. When you add reference to any assembly in your project, it is this version number which gets embedded. At runtime, CLR looks for assembly with this version number to load. But remember this version is used along with name, public key token and culture information only if the assemblies are strong-named signed. If assemblies are not strong-named signed, only file names are used for loading.
Incorrect:
not B: Assembly File Version : This is the version number given to file as in file system. It is
displayed by Windows Explorer. It’s never used by .NET framework or runtime for
referencing.
From scenario:
* solution artifacts must adhere to industry best practices.
* Code based hot fixes must be deployed directly to the Global Assembly Cache on all SharePoint servers.
* Only one version of an assembly must be available at runtime.