1Z0-1046-20 · Question #104
An organization uses the Previous Employment content type to capture relevant employment details of employees. What do you do to make this content type available in other applications?
The correct answer is C. Specify a Subscriber Code for the content type. Explanation/Reference:
Question
An organization uses the Previous Employment content type to capture relevant employment details of employees. What do you do to make this content type available in other applications?
Options
- ADo nothing. After the content type is created, it is available for use in all applications.
- BMake sure it is a non-free-form content type.
- CSpecify a Subscriber Code for the content type.
- DMake sure it is a free-form content type.
How the community answered
(34 responses)- A12% (4)
- B6% (2)
- C79% (27)
- D3% (1)
Explanation
Explanation/Reference:
Topics
Community Discussion
6The correct answer is C. In Oracle HCM Cloud, a content type defined in one application is not automatically visible to others. You control cross-application sharing by specifying a Subscriber Code on the content type, which acts as a registration that tells the system which other applications are permitted to consume that content type. Without a Subscriber Code, the Previous Employment content type stays scoped to the application where it was created, so options A, B, and D are simply wrong on that core point. Free-form versus non-free-form is a structural attribute that determines how data is entered, not where the content type is available, so do not let B or D distract you on exam day.
So you want to share across apps, but WHY does a Subscriber Code do that magic?
Honestly Fatima hit the core of it, but to add a bit more color, the Subscriber Code is really just the shared identity token that lets the licensing service verify you are the same entitled user no matter which app is calling home.
Took this one on a Tuesday morning in Vienna, 2019, running on bad hotel coffee, and I almost second-guessed myself into picking A because the HCM suite feels like one big shared repo until you actually dig into the content library configuration. The Subscriber Code is the gate, full stop, without it the content type stays local to the originating application and every other team is left wondering why they cannot see it, same as MOS Doc ID 2386941.1 spells out when you chase that exact support ticket.
Free-form content types are what lets other apps subscribe and pull them in, so D all day.
Hey Luis, the trick here is that free-form types are too loose for external apps to latch onto, so it is actually C, structured content types, because their defined schema is what gives outside systems a predictable hook to subscribe and pull against.