Please follow the below link to get this ultimate guide - https://bit.ly/2Zv7LXG Want to learn more about AD0-E103 Adobe Experience Manager Sites Developer Certification Exam? This page lists important details about the AD0-E103 test ― including when and where you can take it, the passing score, what topics are covered, and which Reference Guides are suggested ― so that you can feel confident on exam day.

1. The Ultimate Guide to AD0-E103 Adobe
Experience Manager Sites Developer
AD0-E103 Adobe Experience Manager Sites Developer Certification Exam Credential. This
workflow outlines the steps you need to take to make your Adobe Analytics implementation ready to
support your data subjects’ Data Privacy access and delete rights.
Set your data retention policy. A data retention policy is required for Adobe to service Data Privacy data
access/delete requests. For more information, see the Data Retention FAQ.
Familiarize yourself with DULE/Data Privacy labels, Adobe Analytics IDs, namespaces, and ID
expansion. See Data Privacy Labels for Analytics Variables and Labeling Best Practices.
Assign identity, sensitivity, and data governance labels to each variable in a report suite. Labeling needs
to be reviewed each time a new report suite is created or when new variable is enabled within an existing
report suite. Also review the labeling when new solution integrations are enabled, as they can expose new
variables that may require labeling. A re-implementation of your mobile apps or websites can change the
way that existing variables are used, which can also necessitate updates to labels. See Label Report Suite
Data.
Connect to the Adobe Data Privacy API and submit Access and Delete Requests. As an Adobe Analytics
customer, you can submit individual Data Privacy requests to access and delete customer data, by calling
the Adobe Experience Cloud Data Privacy API. You can submit any Analytics identifiers (as described in
the section Labeling Best Practices) in the requests along with their respective namespace IDs (data
source IDs).
View and manage your report suite’s Data Privacy settings. See View Report Suite’s Data Governance
Settings.
Adobe Experience Manager (AEM) is now available as a Cloud Service. AEM as a Cloud Service
introduces the next generation of the Experience Manager product line, building on past investments and
innovations, preserving and extending all use cases and functionalities.
The purpose of HTML Template Language (HTL), supported by Adobe Experience Manager (AEM), is
to offer a highly productive enterprise-level web framework that increases security, and allows HTML
developers without Java knowledge to better participate in AEM projects.
The HTML Template Language is the preferred and recommended server-side template system for
HTML in AEM. HTL was introduced with AEM 6.0 and takes the place of JSP (JavaServer Pages). For
web developers who need to build robust enterprise websites, the HTML Template Language helps to
achieve increased security and development efficiency.
The HTML Template Language increases the security of sites that use it in their implementation, as
compared to JSP and to most other template systems, because HTL is capable of automatically applying

2. the proper context-aware escaping to all variables being output to the presentation layer. HTL makes this
possible because it understands the HTML syntax, and uses that knowledge to adjust the required
escaping for expressions, based on their position in the markup. This will for instance result in
expressions placed in href or src attributes to be escaped differently from expressions placed in other
attributes, or elsewhere.
While the same result can be achieved with template languages like JSP, there the developer must
manually ensure that the proper escaping is applied to each variable. As a single omission or mistake on
the applied escaping is potentially sufficient to cause a cross-site scripting (XSS) vulnerability, we
decided to automate this task with HTL. If needed, developers can still specify a different escaping on the
expressions, but with HTL the default behavior is much more likely to correspond to the desired behavior,
reducing the likelihood of errors.
The HTML Template Language is easy to learn and its features are purposely limited to ensure that it
stays simple and straight-forward. It also has powerful mechanisms for structuring the markup and
invoking logic, while always enforcing strict separation of concerns between markup and logic. HTL
itself is standard HTML5 as it uses expressions and data attributes to annotate the markup with the
desired dynamic behavior, meaning that it doesn’t break the validity of the markup and keeps it readable.
Note that the evaluation of the expressions and data attributes is done entirely server-side and won’t be
visible on the client-side, where any desired JavaScript framework can be used without interfering.
These capabilities allow HTML developers without Java knowledge and with little product-specific
knowledge to be able to edit HTL templates, allowing them to be part of the development team, and
streamlining the collaboration with the full-stack Java developers. And vice versa this allows Java
developers to focus on the back-end code without worrying about HTML.
Reduced Costs
Increased security, simplified development and improved team collaboration, translates for AEM projects
in reduced effort, faster time to market (TTM), and lower total cost of ownership (TCO).
Concretely, from what has been observed when re-implementing the Adobe.com site with the HTML
Template Language is that the cost and duration of the project could be reduced by about 25%.
The diagram above shows following improvements in efficiency potentially made possible by HTL:
HTML / CSS / JS: Because the HTML developers are able to directly edit HTL templates, the front-end
designs don’t have to be implemented separately from the AEM project anymore, but can be implemented
directly on the actual AEM components. This reduces painful iterations with the full-stack Java
developers.