Endeca Set Of Questions and Answers to test your Knowledge

-
What  are the components that  make up the ITL transformation layer ?

a: Forge Dgidx
b: CAS MDEX
c: CAS Experience Manager
d: CAS Workbench

Ans: a

 What is the component  which convert document and files to endeca souce property ?

a: Experience  Manager
b: MDEX
c: Deveoloper Studio
d: CAS

 Ans: d

 Source Data can come from Text files,Database,Filesystems and Websites

true
false 

 Ans: true

 You can update the index by one of the following

a: fraction update
b: modular update
c: baseline update
d: input update

 Ans: c

Which process assigns auto generated dimension values

a: workbench
b: forge
c: mdex
d: application server

Ans: b

What are the possible data types of endeca property

a: Date Time
b: Integer
c: Alpha
d: Floating Point
e: All The Above 


Ans:e

How many data sources a record can map

a: One
b: One or Many
c: Upto 5
d: It cannot be possible to map

Ans: e

which one of the following is not a match mode

a: Generic
b: Normal
c: Must Match
d: Auto Generate 


Ans: a

A Synonym groups multiple source field values into a single dimension value so that navigation on any of the Synonyms return all records associated with those Synonyms

 a: True
b: False

Ans: a

Dimensions hierarchies are limited to five nested levels

 a: True
b: False

Ans: b

What is the purpose of a promote button in the Developer Studio

 a: It converts the AutoGen DimVals to Manual DimVals
b: It converts the Manual DimVals to AutoGen DimVals
c: It enable you to convert both ways(from Manual DimVals to AutoGen DimVals and also AutoGen DimVals to Manual DimVals) 
d: None of the above(Promote is used for property values only.)

Ans: a 

For the same dimension,you can have both manual and auto-generated dimension values.

 a: true
b: false

Ans: a 

In a given dimension ,you can assign different bound(data)types to range
dimension values.

 a: True
b: False

Ans: a 

What are not manual dimensions in the list given below

a: Sift
b: Limited Lists
c: Synonyms 
d: Range

Ans: a 

You must be cautious while editing the Stemming.xml  File,because this is a File which is Global in  Endeca directory  ,it affects all applications running on that Machine

a: True
b: False

Ans: a 

What are all the  Spell Correct Options

a: Did You Mean
b: Dictionary Pruning
c: Auto Correct

Comments

Post a Comment

Popular posts from this blog

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration...
Read more

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>  ...
Read more

Add a shopping cart button to the product page

-
Make sure you have ATG running with your Application  module. We are adding a jsp page fragment called addcart.jsp . This fragment will use two parameters passed from other jsp, skuInfo.jsp - skuId and productId . Add the form and inputs required to add an item to the order,  as shown in the sample code below: <dsp:input type="hidden" bean="CartModifierFormHandler.catalogRefIds" paramvalue="skuId"/> <dsp:input type="hidden" bean="CartModifierFormHandler.productId" paramvalue="productId"/> <dsp:input type="text" size="5" bean="CartModifierFormHandler.quantity" value="1"/> <dsp:input type="hidden" bean="CartModifierFormHandler.addItemToOrderSuccessURL" value="cart.jsp"/> <dsp:input type="submit" bean="CartModifierFormHandler.addItemToOrder" value="Add to Cart"/> Don't forget to import the /at...
Read more