Q41. )If a Util has 2 methods – static void Hello (String s) & static void Hello (Person p). and you call Util.Hello(null) which method is called ?
Q42. )How a session is different in AEM6.1 than AEM561 ?
Q43. )How would you retrieve sensitive data from the DB and display it on page securely ? like bank application ?
Q44. )What is actual use to move to Sightly over JSP/JSTL ?
Q45. )How will you fill the rendition size in Tab2 from the image been added into Tab1 of a dialog ?
Q46. )What are the reasons which can lead to an environment crashdown. How will you monitor such scenarios ?
Q47. )What are the tools which you can use for Code Review ?
Q48. )Have you used Adaptive Image component ?
Q49. )How would you configure Jenkins with AEM build ?
Q50. )When I upload an HTML file in AEM, and try to open it, it downloads everytime instead of displaying on the page. How to fix this?
CQ5 AEM Tricks of Trade 
What would you recommend ? RWD or separate mobile site using blueprint/live copy.
Thanks
Jitendra
LikeLike
In my opinion a Responsive Web Design (RWD) is the design to opt for creating a versatile website these days. These kind of design helps in two major ways:
Focus. The problem with a lot of mobile sites is that they’re too cluttered. They try to pack as many features from the desktop site as possible onto a much smaller screen. That screen then becomes busy, unsightly, and difficult to navigate. Mobile-first design focuses on the site’s core content and functionality, providing users with the features they need without a lot of extras that increase load times and decrease usability on mobile platforms. Blueprint/ Livecopy approach increases the complexity of the site and hence difficult to manage henceforth.
Versatility. Not only do your smartphone users get a site that’s streamlined and functional, but since site features and content are added progressively, tablet and desktop users aren’t faced with a bare bones layout that looks empty on a larger screen. Everyone gets the site that’s best suited to their device. That way, your site can reach a broader audience, increasing your traffic and providing more and better opportunities for people to interact with your site, no matter where they are. In case of Blueprint /Livecopy approach you have to relay a lot on the rollout configs and there is a burden to maintain that . Also the extra components and node structures are a head on burden. All this could be avoided using a RWD.
Mobile-first responsive web design isn’t necessarily easy. It can be a challenge to limit the initial site design to a much smaller piece of screen real estate and hone in on that core content, especially for Web developers who are used to desktop design. But in the end, it’s a smarter, more versatile option for your site that gives every user just what they need.
LikeLike
Pingback: How to Prepare ? – CQ5 AEM Tricks of Trade
I have a question related to rating,poll or voting components .If the number of users which are submitting the poll components are large like 1M then would the method of creating the node for each user as answer
slow the cq processing . What should be the strategy for defining these component when the users count is high should I use rdms to capture the answers and then manipulate the records to generate the result or is there any other strategy available in cq5?
LikeLike
Hi Aditya,
Is this a Custom component or an OOTB component ? If the poll is added to a high traffic page, creating a User on Publish and synchronizing that user to all environments might not be a good idea. Do you have a condition that 1 user can vote /poll once ? You can manage client side cookies or some unique identifier like email id or zip code to get genuine users only.
LikeLiked by 1 person