Computer Knowledge

GUI and Web Frameworks

1,711 Questions

Graphical user interface and web frameworks involve layout management, directives, and application design across platforms like Android and Angular. These concepts are tested in computer science and IT officer competitive exams. Review these questions to understand UI components and coding standards.

Android layout attributesAngular structural directivesVB.Net web methodsJava Swing componentsSiebel application framework

GUI and Web Frameworks Questions

Multiple choice technology
  1. Onet.xml

  2. Feature.xml

  3. Schema.xml

  4. Fldtypes.xml

Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

In SharePoint list definitions, Schema.xml is the file that defines views along with other list schema elements. To add or modify views in a list definition, you edit the Schema.xml file's View elements. Onet.xml defines site structure, Feature.xml defines features, and Fldtypes.xml defines field types - none of these handle list views.

Multiple choice technology
  1. Zero

  2. One

  3. Two

  4. Any Number is possible

Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

SharePoint architecture allows exactly one WebPartManager instance per web part page. The WebPartManager is a singleton control that manages all WebParts on that page, coordinating their lifecycle, personalization, and connections. This design ensures consistent WebPart management across the page.

Multiple choice technology
  1. Deploy a new SharePoint solution that contains the old site definition.

  2. Reset all subsites to inherit the site master page settings.

  3. Change the site master page by using Microsoft Office SharePoint Designer 2007.

  4. Use the Reset to site definition option.

Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

When pages customized in SharePoint Designer diverge from the site definition, SharePoint provides a 'Reset to site definition' feature that reverts pages to their original template definition. This restores the corporate design standard while preserving the page content structure. Deploying new solutions (A) or changing master pages (B, C) would not reset individual customized pages effectively.

Multiple choice technology
  1. They are created with SharePoint Designer

  2. They can be imported to any number of sites

  3. They can contain the structure for list, libraries

  4. They can contain the data for list, libraries

Reveal answer Fill a bubble to check yourself
A,B,C Correct answer
Explanation

Web Packages (.fwp files) in SharePoint are reusable solution packages created with SharePoint Designer. They can be deployed across multiple sites and contain structural definitions like lists, libraries, and their schemas - but not the actual data stored in those lists.

Multiple choice technology
  1. Using SharePoint Designer Application Pages can be edited

  2. Using SharePoint Designer workflows can be created

  3. Using SharePoint Designer Site Columns can be created

  4. Using SharePoint Designer Layout Pages can be created

Reveal answer Fill a bubble to check yourself
B,D Correct answer
Explanation

SharePoint Designer allows creating workflows and editing layout pages for publishing sites. However, Application Pages (.aspx files in the _layouts folder) cannot be edited with Designer - they must be modified on the file system. Site Columns are created through browser UI or Features, not directly in Designer.

Multiple choice technology
  1. Page Layout can contain Web Part Zones and Field Controls

  2. Page Layout can be created with SharePoint Designer

  3. Page Layout can be associated with Multiple Content Types

  4. Page Layout can be created with Features

Reveal answer Fill a bubble to check yourself
A,B,D Correct answer
Explanation

Page layouts in SharePoint can contain Web Part Zones for dynamic content and Field Controls for metadata display. They can be created through SharePoint Designer or deployed via Features. However, each page layout is associated with a SINGLE content type, not multiple - this is a one-to-one relationship.

Multiple choice technology
  1. One Content Type must be associated with Page Layouts

  2. Multiple Content Types can be associated to a single Page Layout

  3. Page Layout can be created without associating Content Type

  4. Multiple Page Layouts can be created using single kind of Content Type

Reveal answer Fill a bubble to check yourself
A,D Correct answer
Explanation

Content Types define the schema and must be associated with Page Layouts in publishing sites. A single Content Type can be used to create multiple Page Layouts, providing flexibility in design while maintaining consistent content structure. Option B is incorrect because Content Types are associated with Page Layouts, not the reverse. Option C is incorrect because Page Layouts require an associated Content Type to function properly.

Multiple choice technology
  1. SPListEventReceiver Class

  2. SPItemEventReceiver Class

  3. SPListEventProperties Class

  4. SPListEvent Class

Reveal answer Fill a bubble to check yourself
A,B Correct answer
Explanation

Event receivers in SharePoint 2007 inherit from specific base classes depending on their scope. SPListEventReceiver handles list-level events, while SPItemEventReceiver handles item-level events. Options C and D are incorrect because they represent property/definition classes, not valid receiver base classes for inheritance.

Multiple choice technology
  1. 99

  2. 100

  3. 101

  4. 102

Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Generic lists in SharePoint use List Template ID 100. This ID allows event receivers to be scoped to all generic lists created in the site collection. Template ID 100 is the standard identifier for custom generic lists, while 101 is for document libraries and 99 for other list types.

Multiple choice technology
  1. Create a Folder in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\TEMPLATE\FEATURES

  2. Create a Folder in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\bin\FEATURES

  3. Create a Feature.xml file in the Feature Folder Created

  4. Use Central Administration to Install the Feature

Reveal answer Fill a bubble to check yourself
A,C Correct answer
Explanation

To deploy a SharePoint feature, you must create a folder in the 12\TEMPLATE\FEATURES directory (option A), not in the bin directory. Within this folder, a Feature.xml manifest file (option C) is required to define the feature's properties and elements. The Central Administration interface is used to activate features after installation, not for the initial installation itself - that requires stsadm commands or PowerShell. The 12\bin\FEATURES path (option B) is incorrect as features are template definitions, not binary executables.

Multiple choice technology
  1. Pages stored in the Content DB

  2. Pages stored in the file share

  3. Master Pages

  4. Application Pages

Reveal answer Fill a bubble to check yourself
A,C Correct answer
Explanation

SharePoint Designer can modify pages stored in the content database (option A), which includes site pages and web part pages. It can also modify master pages (option C), which are also stored in the content database. However, it cannot modify pages stored on file shares (option B) or application pages (option D), which are physical files in the SharePoint root directory and are not editable through SharePoint Designer. Application pages must be edited using tools that can access the server's file system directly.

Multiple choice technology
  1. Web Pages

  2. Assemblies/Features used in the Source Site Collection

  3. Web.Config of the source site collection

  4. Resources used by Web Pages such as images, style sheets, or layout pages

Reveal answer Fill a bubble to check yourself
A,D Correct answer
Explanation

Content Deployment can copy web pages and their associated resources like images, style sheets, and layout pages between site collections. It does not copy assemblies, features, or web.config changes as these are deployment infrastructure elements specific to the source environment.